How LumiFrame Founder Casey Schneider Built a Reliable Smart Photo Display SaaS

The frustration was realizing how many photos and videos I had taken and how few I actually saw again. I had spent years working in IT and as an editorial portrait photographer with two children; media was already a humongous part of my life. But once these "memories" went into the cloud or my dusty NAS, they usually stayed there unless I deliberately went looking for them. I started looking for a good way to put them on a screen in my home. The existing apps felt stupidly dated or awkward or gated behind a paywall, and the thought of buying another dedicated device also felt unnecessary when I already had everything I needed. That iPad from 8 years ago, let's use that! This became the starting point for LumiFrame - to make the screens people already own useful as living photo and video displays. So, I set out to do just that, all without a plan!

What worked was being personally invested in what I was building. Life was in an unprecedented dark and hard time for me, so I sunk my entire being into it as an escape. What I strived for was a product that is gorgeous to look at, powerful, and easy to use. Usually, that sounds like one of those “here are three things, pick two” situations, but I wanted all three. That stubbornness kept me going through the less exciting work, and the personal ties only hardened that. When I say I put in my time, I really mean that I put in my time. What didn’t work was vibe coding without a plan. It made starting easy, but eventually I was building on decisions I hadn’t really thought through. I’d add something, discover the foundation didn’t fit anymore, and end up rebuilding a huge chunk of the app. At this point, it feels like I’ve rebuilt LumiFrame 5 times!

The feedback I take most seriously is friction. Something might work most of the time, but if someone brings one or two blips to my attention, I’m all over it. What feels like a small issue from the development side can be the moment someone starts questioning whether they can depend on the whole product. I want LumiFrame to feel effortless. People shouldn’t have to wonder whether something worked, repeat an action just to be sure, or learn little workarounds. They should be able to enjoy their memories without thinking about the software making that possible. When an issue comes up, I want to understand what the person experienced, find the cause, and make sure the fix actually holds up. I also look for where the same friction could happen elsewhere, because fixing one instance isn’t enough if the underlying problem is still there. Reliability builds trust, and trust is everything. People are trusting LumiFrame with moments they care about. Taking even the occasional blip seriously is part of respecting that trust.

I think people underestimate how different displaying photos is from storing them. Most of us already have somewhere to upload the 13,000 pictures and videos we have on our phones. The missing part is a reason to revisit them repeatedly, especially without having to constantly dig for them. The digital frame market starts with a hardware purchase. Plenty of people already own a screen that could serve this purpose. Software can let them try the experience before deciding whether they want to dedicate a device to it. It is also easy to reduce the audience to grandparents and families. That is an important use, but the same idea applies to a photographer showing their work, guests contributing to an event album, or a small business choosing signage in their space. What matters is giving people control over which images belong in a particular room and who can contribute, rather than assuming every screen should show the same collection to everyone.

Making the core experience feel more polished and dependable by having an easier setup, smooth photo and video playback, and clearer control of connected displays. I also want shared albums and event contributions to feel natural for people who have never used LumiFrame before. The Reflections engine is the trickiest part when it comes to helping people reconnect with meaningful moments instead of adding more noise. I will judge this by how people keep using their displays, rather than more features.

4 platforms and Windows support on the way, iOS, Android, Web, Mac. Built by one person!

I came into LumiFrame with 17+ years of IT experience and a background in photography. IT gave me the instinct for troubleshooting and noticing how systems work. Photography gave me the concern of whether a memory is actually presented in a way that makes someone want to look at it. Building a consumer product brought those interests together, but it also meant learning things beyond my skills. Designing an interface, handling subscriptions, supporting multiple platforms, and helping people all land on my shoulders. I am the founder, designer, and developer, so I see both the creative decisions and the consequences.

My biggest mistake has been allowing the product’s breadth to get ahead of how clearly I explain it. When you build something yourself, every feature feels connected because you know why it exists. A new user doesn’t have that context, and showing them everything at once can make a useful product feel overwhelming. I’ve learned to start with one understandable job, choose some photos and videos, put them on a screen, and enjoy them. Sharing, remote management, and everything else LumiFrame does should support that first success and become relevant when someone needs them. I learned quickly that completeness isn’t the same as usefulness. A feature only adds value when people understand how it helps them.