We build travel software, and we build for other people.
SevichaApps makes mobile products for people who travel, starting with Sevi, and builds the same kind of thing for other companies. Small enough that the person who wrote the code reads the support mail.
Sevi is ours end to end — the planning, the AI, the servers behind it and both store listings. Nothing is white-labelled and nothing is outsourced.
A model writes the itinerary because that is a job it does well. The rest of the app is ordinary software, because a chatbot is a poor way to split a restaurant bill.
We built the morning weather notification to store your location, then rebuilt it so it does not. The nudge is worth less that way. Keeping your position off our servers is worth more.
We build for other companies too.
Everything below is something we have shipped in Sevi and run in production, not a capability list. If you want the same work done on your product, that is the arrangement.
One codebase, Android and iPhone, with the native work where it is actually needed. We have taken a product from an empty repository to a store listing, and we know which parts of that take the longest.
Structured output rather than a wall of prose, keys held server-side rather than shipped in the binary, and a cost per request you can actually quote. The unglamorous half is what makes it survive real traffic.
Subscriptions and one-off purchases verified on a server, ads with consent handled properly for every region, and the privacy declarations both stores ask for before they will publish you.