This is not a client engagement. Ailifestory is ours: we designed it, we pay for it, we ship it through TestFlight toward release. It is on this page because a studio that claims it can put AI systems in front of real users should be able to point at something it put in front of real users.
The first version solved the wrong problem
Ailifestory started in 2023 as a web product with a simple pitch: an AI interviews you about your life, and you get an autobiography out of it. The interview worked. The writing worked. The book was the problem.
A book is a single, terminal artifact. You finish it, and the product is over. Worse, it sets a bar - a book - that makes the first session feel like the start of a large obligation rather than a fifteen-minute conversation with your mother. The people we most wanted using it were the people least likely to start.
What it is now
A native iOS app built in SwiftUI, rebuilt from the Expo version rather than patched. The unit of value moved from the finished book to the recurring moment:
- Voice interviews. You talk. The app asks the next question. Nobody has to write anything.
- A private family feed. Stories land somewhere the family can see them, so the person telling them gets a response instead of a progress bar.
- Weekly episodes. Recordings are cut into a podcast-style episode each week - something that arrives on its own, which is what turns a project into a habit.
- An App Clip. Sharing a story with a relative does not require talking them through an App Store install first. They tap, they hear it.
- Home-screen widgets. The prompt to record sits where the phone already is.
Going native was the enabling decision for most of that list. App Clips, widgets, and audio that behaves correctly in the background are not things you bolt onto a cross-platform shell late.
Why it is on a studio site
The engineering discipline is the same one the enterprise work runs on, at a much shorter feedback loop. It ships through Xcode Cloud, has a full App Store Connect and TestFlight release trail, and carries real subscription infrastructure rather than a demo paywall. Shipping to people who did not agree to be a pilot is a good way to keep an honest opinion about what "in production" means.
The company work and the app work are not separate practices. They are the same team finding out whether its decisions survive contact with users.