The Phone Is the Tool, the Desk Is Still There

In the last post I named who FediFlick Archive is actually for: people using a photograph to hold onto memory, family, and place, not to make it look better. I ended by promising to explain why the phone, not the desktop, is where this actually starts, and why that’s not the whole story. Here’s that promise kept.

Where the Story Actually Happens

Picture standing in front of an ancestor’s old house, or at a gravesite you’ve been trying to find for years, or on a street that shows up in one faded family photo with no caption at all. The photograph and the story arrive together, right there, in that moment. Whoever you’re with says something like “this is where your great-grandmother used to stand and wave us off,” and if that sentence doesn’t get captured alongside the photo, in the next five minutes, it’s gone. You can take the photo now and write it up properly later at a desk, sure, but “properly later” is exactly where most of the actual content of that sentence quietly evaporates.

The same thing happens, in a different register, sitting with an older relative and a shoebox of prints. They start telling you who’s actually in a photograph you’ve looked at fifty times without knowing. That’s a reminiscence conversation happening in real time, and you get roughly one honest shot at it. A tool that asks you to remember the details and enter them properly once you’re home again has already lost most of what made the moment worth capturing in the first place.

That’s the actual case for mobile-first here. Not “phones are convenient,” which is true of almost anything and explains nothing. It’s that the photo and its context exist in exactly the same moment, in the field, and the gap between that moment and a desk is where the story leaks out.

What’s Already Shipped

None of this is a future promise. FediFlick’s composer is built image-first today: you start by picking the photo, not by opening a blank text box, and the app then walks you through a structured Title, Description, and Tags layout rather than one undifferentiated field. Alt text is mandatory on every image, not an optional afterthought you can skip past, which sounds like an accessibility detail and is one, but it also happens to be exactly the muscle a genealogical caption needs anyway: what’s actually in this photograph, spelled out, for someone who wasn’t there. The tool built for accessibility and the tool built for family history turn out to want the same discipline.

The Desk Doesn’t Disappear

Not every session looks like the scenarios above, though. Digitising forty-year-old prints happens at a desk, with a scanner, over a weekend, not out in a field with a phone. Someone going through a late relative’s boxes is usually sitting still, working through a pile, not standing somewhere with a story unfolding in front of them.

FediFlick runs on desktop too, for exactly that workflow, and it’s not a cut-down companion to the mobile app, it’s the same tool: the same image-first composer, the same mandatory alt-text discipline, the same posting pipeline out to Mastodon, Bluesky, Pixelfed, Nostr, and Flickr. Flutter is what makes that a single codebase rather than two separate apps to maintain. What differs is the unglamorous plumbing underneath, filling in for things phones get for free. There’s no Android- or iOS-style share sheet on desktop, so there’s a built-in file picker instead. There’s no OS-level handler to catch a login redirect, so authentication falls back to a brief local web server rather than the app-link flow a phone gets automatically. Small differences, not a lesser experience. I’ve built and tested this on Linux specifically because that’s my own desk, not because there’s anything Linux-specific about the design.

Different workflow, same tool. Which one you reach for depends on whether the story is unfolding in front of you right now, or waiting patiently in a box that’s been closed for years.

Not Every Camera in the Field Is a Phone

There’s a third case I skipped past above, and I shouldn’t have, because it isn’t rare and it isn’t the craft/editing crowd from the last post either. My friend Michael, the one whose feed I mentioned following back in the very first post of this series, won’t touch a phone for photography. He shoots with a Sony point-and-shoot he’s had for years, one with GPS built in, and he’s told me flatly there’s no upgrade path for it anymore.

I checked that claim rather than taking it on faith, and it holds up, with one nuance. It’s not that no camera anywhere still has GPS, but it’s close enough to true for Michael’s actual situation to sting. Sony’s own GPS-equipped Cyber-shot compacts, the “V”-suffix models like the HX90V, haven’t had a new entry since around 2014, and Sony’s more or less walked away from that whole category since. What GPS survives in cameras today lives almost entirely at two extremes that don’t help him: professional flagship bodies costing thousands, built for a completely different job, and rugged “tough” outdoor compacts built for hiking and diving, not the sleek everyday travel camera he actually wants replaced. The elegant, built-in-GPS travel compact he’s used for years simply isn’t a category anyone makes anymore.

None of that is a problem for FediFlick, though, and here’s why. FediFlick isn’t a camera app, it’s a posting layer, the same separation of concerns I described back in the first post of this series, just applied one step earlier. It doesn’t care whether a photo arrived via a phone’s own camera, a Sony point-and-shoot transferred over afterwards, or a flatbed scanner. If the file’s there, with its GPS EXIF intact, exactly the kind of metadata Michael’s camera has always written and plenty of phones quietly strip or complicate through their own photo-management layers, FediFlick can read it, offer it up while writing the caption, and post it, from the phone or from the desktop app, whichever he actually reaches for once he’s home. The moment in the field where a photo and its story happen together, the actual argument of this whole post, doesn’t require the device making the photo and the device doing the posting to be the same device at all.

Michael’s Sony will probably outlive its own manufacturer’s interest in supporting it before anything else does. That’s a small, oddly on-theme example of exactly the kind of quiet feature loss this series keeps circling back to. FediFlick, at least, isn’t going to be the reason his GPS-tagged photos stop mattering.

What Isn’t There Yet

Better to be honest about the gap than smooth over it. Groups as a shared, standing archive, the actual community layer this is all building toward, isn’t built. Neither is voice capture as a genuinely first-class input alongside text, and for a good chunk of this audience, especially the reminiscence conversation with an older relative, that matters more than it sounds like it should. Holding a phone up while someone talks is a far lower barrier than asking them to write anything down, or asking you to type fast enough to keep up while they’re mid-story. Right now that’s still a plan, not a feature, and I’d rather undersell it than let the mobile-first pitch above sound more finished than it is.

Where I Could Use Help

One more honest gap, a practical rather than a design one this time. Day to day, I only actually build, run, and test this app on Android and Linux, simply because that’s the hardware on my own desk. Flutter supports macOS, Windows, and iOS natively, and the stated plan is genuinely to cover the common combination, Linux, macOS, and Windows on desktop, Android and iOS on mobile, not just the two platforms I happen to carry around. I haven’t touched those other three in any serious way yet.

That’s partly why I’m writing this series in public rather than quietly building in a corner: I want to know if any of this actually resonates before I spend more time on it, and if it does, I’d genuinely like to hear from two kinds of people. One is anyone who’d actually use something like this, documenting a subject, a family, or their own past, and would rather it existed than didn’t. The other is anyone on macOS, Windows, or iOS willing to help test, or help with build and compile support on a platform I don’t touch daily myself. Both are real, concrete ways to help this go from a plan to something worth trusting.

Part three of five in the FediFlick & Digital Commons series. Previously: Who FediFlick Archive Is Actually For. Next: Archives That Outlive Their Contributors.

Sources

• FediFlick project documentation (README.md), for the shipped image-first composer, mandatory alt-text, and desktop implementation details (file-picker fallback, OAuth loopback server) cited above.
• “The Emerging Role of AI in Life Storytelling for Older Adults: A Systematic Review of Commercial Apps”, ACM, on voice-and-AI-first storytelling tools (Storii, HereAfter AI) as a lower-barrier alternative to typed input for this audience.
• “Why GPS in cameras is going away”, Digital Photography Review forum discussion, and Best Sony Compact Cameras with GPS, CameraDecision, on Sony’s GPS-equipped Cyber-shot “V”-series compacts (e.g. the HX90V) having no new entries since around 2014, and built-in GPS today surviving mainly in professional flagship bodies and rugged outdoor compacts, not everyday travel compacts.

Related reading: Who FediFlick Archive Is Actually For, on the audience this whole series keeps coming back to.

• FediFlick
• Photography
• Mobile
• Genealogy
• Local-First
• Digital Commons
• Open Source