"Ship and support" is one of our stated values, and it's worth being specific about what it actually means in practice, because it's the kind of phrase that's easy to say and easy to quietly abandon once a product is live.
For us, it means every app on this site is still being actively maintained — bugs get fixed, Play Store and platform requirements get kept current, and features keep evolving based on what users are actually asking for, not frozen at the state they launched in.
"Platform requirements get kept current" sounds like a minor administrative detail, but it's one of the more common places software quietly dies. App stores update their policies, target API levels and privacy requirements regularly, and an app that isn't actively maintained against those changes eventually gets flagged, restricted, or removed — not because anything about the app itself changed, but because the platform moved and nobody kept up. Staying ahead of that is unglamorous, recurring work that never shows up as a feature, and it's exactly the kind of thing that gets skipped first when a team quietly stops supporting something.
It also means we don't launch products we don't intend to keep running. Before we start building something new, we ask whether we're genuinely prepared to support it for years, not just whether we can ship version one — because a church or a business adopting one of our products is trusting us with something they depend on.
That question has stopped ideas we were otherwise excited about. An idea can be technically interesting and still fail the support test — if we can picture ourselves losing interest in maintaining it eighteen months in, once the novelty of building it has worn off, that's a strong signal not to start at all. We've watched other small studios ship something promising, get positive attention for the launch, and then quietly stop responding to support requests within a year — and we'd rather turn down an exciting idea than become that story for one of our own users.
Launch day gets the announcement. Everything that happens after is the actual commitment, and it's the part we take more seriously — the unglamorous years of bug fixes, platform updates and support emails that never make it into a portfolio screenshot, but are the entire reason a church or business can build real, long-term plans on top of what we've built for them.