What Should You Name a Shared Photo Album?

The album nobody named

Naming an album happens at the worst possible moment. You have just come back from ten days somewhere, you are holding four hundred photos, and a box appears asking what to call them. Whatever you type there you type in a hurry, which is why so many shared albums are called Trip, or Photos, or the date they were uploaded, or nothing at all.

The name matters more than it looks like it does, because it is the thing the person you send it to sees first, and the thing you will scroll past looking for it in two years. A good one is almost always the same shape: a place and a time. Lisbon in April. Christmas at my parents'. Nobody needs to be taught that shape. They just need to not be asked to produce it while they are tired.

What a photo already knows about itself

A photograph off any phone or camera of the last fifteen years carries a block of EXIF metadata, and two of its fields are exactly the two halves of that sentence. DateTimeOriginal is the moment the shutter fired. GPSLatitude and GPSLongitude are where you were standing, each paired with a reference tag saying north or south, east or west. That is it. That is the whole input.

The reference tags are worth a sentence of their own, because they are the easiest thing in this to get wrong. Latitude is stored as a positive number with a separate letter beside it, so a photo taken in Sydney and a photo taken in Tokyo can hold the same three numbers and differ only in a single character. Read the coordinate and skip the letter, as a filtered metadata parser will happily do, and every southern hemisphere photo silently moves to the northern one.

Viallo is a private photo sharing platform for albums you send as a link: viewers open them in a browser with no account, photos stay at the resolution they were uploaded at, and nothing on the server reads the pictures themselves to train a model. Grouping an album by the places in it has been part of it for a long time. Naming the album after those places is the newer half, and it runs in the browser, on the files you just picked, before a single one of them has been uploaded.

Sixteen photos is enough to see a trip

Reading four hundred files to name one album would be slow and pointless. The sample is capped at sixteen, spread evenly across the selection and always including both ends, which is the cheapest way to see a trip that started in one country and finished in another. Below sixteen photos, everything gets read.

The positions that come back are then grouped onto a one-degree grid, which is roughly a hundred kilometres. That number is a claim about titles rather than about geography: two photos ninety kilometres apart are not two places worth naming separately, and two photos three hundred kilometres apart usually are. The eight heaviest groups survive, ordered by how many photos fell into each, and each one keeps a real coordinate from inside it rather than the rounded corner of its grid cell, so the place lookup is asked about somewhere that exists.

Those eight coordinates go to the server in one request instead of eight, and the server checks its own store of previously resolved places before it asks any geocoding provider at all. A trip round Japan mostly resolves out of places somebody already looked up.

The grammar that turns two facts into a sentence

Having a list of places and a range of dates is not the same as having a title. What turns one into the other is a set of rules about how specific to be, and the rule is that specificity should fall as the trip gets bigger. One country gets named by its cities. Two or three countries get named as countries. Four or more stop being a list at all.

The time half narrows the same way. One day is a date. A few days inside one month is the month. Anything longer that still sits inside one season is the season, so ten days in July reads summer 2024 rather than July 2024, which is how a person would describe it. Two months either side of new year read as one winter, written winter 2024-25. Anything wider falls back to a year, or a pair of them.

June is not summer everywhere

This is the first of the four places the sentence goes wrong, and it is the one that reads as an insult rather than a bug. Photos taken between 10 June and 20 August in Tokyo are Tokyo in summer 2024. The identical dates in Sydney are Sydney in winter 2024. The month is not the season. The month plus the hemisphere is the season, and half the world lives in the half that most software forgets.

The fix is not a lookup table of countries. It is the sign of the latitude that is already sitting in the file: negative is south, and the season table for the south is the northern one shifted six months. December to February in Sydney comes out as summer 2024-25, crossing the new year exactly as a northern winter does.

Then there is the trip that goes to both. An album with photos from Sydney and photos from Tokyo has no season, because both answers are defensible and they contradict each other, and a title that confidently picks one is worse than a title that does not mention it. So it does not mention it: Australia & Japan in 2024. If the dates happen to sit inside one month it still says the month, because a month is true in both hemispheres. Only the season is thrown away, and only when the album is the thing that made it ambiguous.

The same album, two phones, one title

Here is a failure nobody would predict from the outside. Android hands a photo picker's selection back newest first. iOS hands it back oldest first. Nothing about that is wrong, and it does not matter for anything else, but it means two people selecting the identical forty photos hand them over in opposite orders.

That leaks into the title in two ways if you let it. It decides which end of the trip gets sampled if you read the first sixteen files rather than spreading the sample, and it decides which of two equally weighted places gets printed first. The same album could come out Tokyo & Kyoto on one phone and Kyoto & Tokyo on the other, which is the kind of inconsistency that makes a feature feel unreliable without anyone being able to say why.

So the sample deliberately covers both ends, and a tie in photo count falls to the northernmost place, with longitude settling a shared parallel. Both rules are arbitrary. That is the point of them: an arbitrary rule applied the same way everywhere produces the same title on every device, and there is no defensible non-arbitrary answer to which of two equally photographed cities should come first.

Where it gives up, and why that is the right answer

Plenty of photos carry no location at all. Screenshots never do. Photos sent through a messaging app usually arrive stripped. On Android, the gallery hands most apps a copy with the coordinates removed unless the app both holds the right permission and asks for the original file, which is a whole problem of its own.

When the selection carries nothing readable, no title is offered and the album keeps its default name. That is a deliberate choice rather than a gap: a made-up title is worse than an empty box, because an empty box is honest about not knowing and a wrong one has to be noticed before it can be fixed. Two other limits are worth stating plainly:

• Only eight groups of places go to the lookup, so an album covering more distinct places than that can come out named after a continent where the dropped ones would have made it Around the world.
• A date with no place uses the northern seasons, because with nothing to contradict it there is no better guess available. A photo from the equator counts as northern for the same reason.

And the title is a suggestion, always. It arrives in the name box filled in, and it is a box, so it can be replaced with two words of your own before anyone else ever sees it.

None of this looks at your photos

It is worth being precise about what is happening here, because "the app worked out what my trip was" sounds like something that required a model looking at the pictures. Nothing did. Every input above is a number attached to the file: a timestamp, a latitude, a longitude. The image itself is never examined, on the phone or on the server. A photo of a cathedral and a photo of your shoes taken in the same street produce exactly the same contribution to the title.

That is a real limit and worth naming as one. Nothing here will ever tell you a photo contains the Sagrada Familia, because working that out means reading the pixels, and reading the pixels is the thing this platform does not do. What metadata alone can do turns out to be most of what you actually wanted: the album already knows it went to Barcelona in October.

If that is the part you care about, the related ground is a travel album laid out on a map, which is the same coordinates used for a different purpose, and creating a shared album from scratch, which is where the name box appears in the first place. Sending it on afterwards is a link that needs no account at the other end.