Deciding for the room
No app event photo sharing, chosen for everyone but you
No app event photo sharing is not a stance about software. It is a decision you take on behalf of eighty other people, none of whom volunteered for a technology rollout and not one of whom will tell you that they gave up halfway.
No app, no account, private by default, downloads you can keep.
Look at a guest list honestly for once and you stop seeing a friendly crowd. You see eighty separate phones, eighty separate data plans, eighty separate relationships with technology, and one occasion that all of them turned up for. The sharing decision is yours to make, but the cost of it lands on them, and it lands unevenly: the identical request is forty seconds for one guest and a small project for another. That asymmetry, not the photography, is what decides how full the collection gets.
What the request actually costs a guest
Asking somebody to install something is the most expensive favour you can request of a person standing at a table with their friends. The price is not one number either. It is storage, data, battery, permissions and an identity, and a different person in the room is paying each one.
- Space on the phone
- For most people the camera roll is the reason the device is full. A couple of hundred megabytes set aside for one evening is a decision about their own phone, and plenty of guests make it in the negative without thinking about you at all.
- Mobile data
- The software is the first download and forty photographs plus two clips are the second, heavier one. A guest on a tight allowance is doing sums about their month while you are doing sums about your pictures, and their arithmetic usually wins.
- Battery
- A new application asked to read a camera roll and push files out is among the hungriest things a phone can do. At half past nine, on a handset that has been taking photographs since four o'clock, that is the moment the screen goes face down for the night.
- Permissions
- Before a single frame moves, an install usually wants the whole photo library, sometimes the camera, often notifications. Someone happy to send you six pictures is not automatically happy to open their entire archive to software they reached through your table card.
- An identity
- Installed software wants to know who is using it, which means an address, a password, and often a code to confirm both. That is a separate errand, in a different part of the phone, and none of it has anything to do with your event.
- Standing still
- Five to ten minutes of a two-hour meal spent not talking to anybody. Guests give that stretch of time to a handful of occasions in a year, and most evenings in the room are not one of them.
The guest who is protecting their data
There is a whole category of person who will not spend their bundle on somebody else's party, and it is a sensible decision rather than a mean one. You will never hear it explained, because it is not an argument anybody makes at a table. It just shows up later as a collection with fewer photographs in it.
- A capped plan at the end of the month, where the next gigabyte costs real money and the guest already knows it.
- Someone roaming abroad, charged per megabyte, who has switched mobile data off altogether to avoid a bill they cannot predict.
- A guest tethering from a phone that is nearly out of allowance because they have been photographing since the morning.
- A venue or hotel network that will load a page happily and then stall an upload halfway through.
- The person flying home tomorrow, saving what is left of their allowance for the airport.
None of these people are being difficult. They are running their own accounts. What a browser page gives them is a choice they can actually take: two frames now on the room's signal, twenty more from the hotel, or nothing at all. Nothing is locked behind a download they cannot afford, and a photograph that arrives on the Tuesday is worth exactly as much as one that arrives during the speeches.
Older phones, shared devices, and who you lose
The four-year-old handset
Compatibility notices are the quietest exclusion in event photo sharing. The store page says the software needs a newer system than the device runs, and the relative reads that as this is not for me rather than the host chose badly.
The family tablet
A shared device signed into somebody else's account is not one anybody wants to install new software on, grant library access to, or leave a saved password on. The grandparent with the best photographs frequently has the oldest screen in the building.
The store that will not cooperate
A guest stuck behind an account password they have not used since the last update never reaches your collection at all. Your request does not fail loudly. It simply never arrives, and from where they are sitting the evening offered nothing.
The one who will not admit it
Nobody at a dinner table announces that they cannot work out a login. They put the phone away, enjoy the night, and say to send me yours afterwards, which is how a host finishes with forty photographs from the four people who were always going to help.
You become the technical department
The cost of an install is not paid only by the guest. It comes straight back to you, in the middle of your own occasion, as a queue of questions you never agreed to answer.
- Which one is it? There are four with a similar name and one of them is a scanner.
- It wants my old email address. I do not remember which one.
- The card says this is not available in my country.
- It is asking to see all my photos. Is that you, or is that them?
- I installed it and now it will not let me sign in.
- Can you just take the phone and do it for me?
That last one is the honest summary of the whole affair. Every minute spent talking somebody through a store page is a minute you are not hosting, and every question you answer at eleven at night is a question that stopped somebody else contributing an hour earlier. The host who asks for nothing technical does not have this evening at all. The pictures arrive while they are still at the top table, and the only support they owe anybody is a pointing of the hand at the card on the cloth.
Two requests, compared honestly
A guest who has to install something
- The ask is a project: find, download, allow, register, confirm, learn the layout.
- It costs storage and data on a device that is not being used for your occasion.
- It needs a piece of the guest's identity, usually an address and a password.
- Every failure is invisible to you and faintly embarrassing to them.
- The software is deleted on the way home, and the good Sunday photographs go with it.
- You end the evening having fielded six support questions at your own party.
A guest who opens a link
- The ask is four small things, and two of them they were doing already.
- It costs a few seconds on a phone that was already in their hand.
- It needs a first name, given once and remembered for twelve hours.
- It behaves the same on an old handset, a tablet and a Sunday laptop.
- The address stays in the browser history, so the late set still lands.
- You spend the night hosting, and nothing else.
Neither column is about the quality of a photograph. The file that leaves the phone is the same file either way. What changes is how many of them leave.
Ask a room to install something and you get the photographs of the people who like you enough to bother. Ask for nothing and you get everybody's.
What no app event photo sharing leaves out
- A download, an install, or an update of anything at all.
- An account, a password, or a confirmation code to open on a second device.
- Permission to read an entire photo library when six frames were wanted.
- A cost, because guests never pay and never see a price on the page.
- A reason to remember the occasion exists tomorrow, beyond the address still being there.
What is left is a browser page carrying the occasion and your names, a file picker, one line for a name, and a send button. That is the whole product from the guest's seat.
How the night goes differently
During the drinks
The eager few go first
The four people who were photographing all afternoon notice the card, send three frames each, and mention it to nobody yet. On the install model this is roughly where the collecting stops, because everyone who follows has to be convinced as well as asked.
Between courses
A table does it in one minute
Food arrives, phones come out anyway, and one person at table six sending photographs without a password makes the idea contagious. Contribution travels sideways through a room far faster than it travels downward from a speech.
After the last dance
The address is still open somewhere
In the taxi, in the hotel bedroom, on the lift home, people look through what they shot and send the two they liked. Nothing has been deleted, so nothing has to be re-downloaded first, and there is no login to remember at midnight.
Sunday
The set nobody thought of on the night
The late arrivals are often the best frames, chosen rather than grabbed. A page left in a browser history collects them for free. An application uninstalled on the Saturday does not get a second chance.
Occasions where an install has no chance
- A wedding with guests flying in
- Half the room is roaming, the other half is on the venue's single access point, and everybody is tired. A code that opens a page is the only request that survives both, because the upload can wait until Thursday without losing the photograph.
- A reunion across three generations
- Cousins aged six to seventy-eight, several of whom share a device. The oldest cameras belong to the people with the oldest phones, which is the exact combination an install request punishes.
- A conference or a works event
- Work phones often refuse new software outright, and personal ones should not be asked to carry a client's tool. A browser page opens on both and asks for nothing that an IT policy has to approve.
- A birthday in a barn or a marquee
- Signal out in the yard, thin walls, no reliable wifi. Nobody is going to start a download in those conditions, but plenty of people will send three pictures from the car park on the way home.
- A leaving drinks on someone else's schedule
- Two hours, forty people, and a room that empties on the hour. There is not a single minute in it during which asking for an install is reasonable.
What hosts ask before ruling out an install
Do my guests really install nothing?
Nothing, on any plan. A code or a link opens a page in the browser already on their phone. There is no store page to find, nothing to register for, and no password to invent at a table.
What if a guest has no storage left on their phone?
Then a page is the only method that works for them anyway. A browser needs no room beyond the upload itself, and the photographs are already sitting in an album the phone organised, so nothing has to be deleted first.
Does sending from abroad cost the guest money?
Any upload over a roaming connection costs data, and that is true of a web page as much as of installed software. The difference is choice: a guest can wait for hotel wifi or go home, and the same address is still there when they do.
Is a browser page worse at quality than an application?
The file your guest chose is stored exactly as it arrived either way. The small preview the grid needs is drawn in the browser on their phone, which is why a full-size picture does not make the page crawl.
What do I tell a guest who does not trust a code on a table?
The same short address printed as text beside it. They can type it later on their own terms, or open it on the laptop they are using at home. Nothing about the method insists on the code.
Is there anybody an install genuinely suits?
Only the guests who would have installed it for reasons that have nothing to do with you. For one evening of collecting, software you delete in the taxi is worth almost nothing, and the asking price is paid by everyone else.
Do I need an app myself to run the collection?
No. The host side is an ordinary web page too, on a phone or a laptop, with the settings, the incoming submissions, the table stands and the download on it. There is nothing to keep updated on your end either.
There is no application waiting in the wings
This product has no iOS or Android version and no plan to build one. A browser page is not a placeholder for a proper install. It is the part of the design that lets a hundred strangers contribute to one collection in a single evening without your help.
Why a page beats an installThe test that settles the argument
If you are not sure whether the install is costing you anything, do not take my word for it. Run the comparison yourself on something small: a dinner for six, a work lunch, a birthday with twelve people. Put the link on the table, ask for nothing, and count what arrives by the weekend. Then do the same event the way you did last time. The gap between those two collections is the entire argument, and it is your own evidence rather than mine.
Take the install out of your next event
Open a collection, print the table card, and let the photographs come in from the browser everybody already has. The free plan runs a real occasion, so the comparison costs you nothing but a dinner party.
How it works
Put one link on the tables and let everyone contribute.
Create a collection, print the table stands, and the photographs your guests took are waiting for you the morning after. Guests never install anything and never make an account.