New Products
We build mobile, web and AI products. We take yours from spec through design to launch, on every platform at once.
We're SwiftKick, a software development firm that builds with AI agents using our SKAI system.
SKAI
Everyone is using the same AI coding agents, and they're good. On their own, though, they write code fast and lose track of the product they're building. SKAI gives them what a good team has, so they can take on your whole product and finish it, quickly and to a high standard.
Holds the product's specs, design and architecture.
Every agent works from it.
Say what happens to a ticket when its rider misses the sailing.
Why Missing a sailing used to void the ticket. Decision D1 changes what a missed ticket is worth.
Why Most riders who miss a boat still travel that day. This follows decision D1, using the answer the agents recommend.
1 Decision D1 is still open. This rule assumes the recommended answer and will change if you choose another.
Why The app in the stores already works this way. This was taken from the existing code.
Why Moving a ticket to another sailing is new, so it needs rules of its own.
Why One move covers a late arrival without letting a ticket stay open for days. This follows decision D2.
Describes how and why the product is changing.
Each change is reviewed before it is built.
Ticket
Ticket now opens Ask for a refund as a modal, beside Boarding pass.
Why A rider whose ticket cannot be moved needs a place to ask for a refund (REFUND-02.02).
A moved ticket says which sailing it was moved from.
The ticket shows its new sailing, with a line saying which one it was moved from.1
Why A moved ticket has to say that it was moved (REFUND-02.01). This follows decision D1.
1 Decision D1 is still open. This is drawn for the recommended answer.
Why The rider still holds a ticket that can be used (REFUND-02.01).
A sheet that opens from a missed ticket when no later sailing has room.
Why The refund needs a place to be asked for (REFUND-02.02).
Why A missed ticket is no longer void. V01 takes its place.
Puts teams of agents on large-scale work.
When a decision is yours, they ask and recommend an answer.
App shell and sign-in
Routes and timetables
Payment account
Fare rules
Sailing search
Rider profile
Card payments
Fare summary
Seat hold while paying
Saved riders
Receipts
Refund rules
Ticket purchase
Boarding pass
Trip reminders
Rebooking
Offline tickets
Group tickets
Trip history
Offline boarding
Release checks
Sailing search
Rider profile
Card payments
Fare summary
Seat hold while paying
Saved riders
Receipts
Ticket purchase
Boarding pass
Trip reminders
Seat hold while paying
A rider's place on the sailing is held for ten minutes while they pay, then let go.
Two riders cannot both buy the last place. A hold that runs out frees it.
A rider misses a sailing. What happens to the ticket?
Reasoning Most riders still travel the same day, and the fare rules already allow a later sailing.
We build mobile, web and AI products. We take yours from spec through design to launch, on every platform at once.
iOS to Android, Android to iOS, mobile to web. The work is in everything your app does that nobody ever wrote down, and we bring all of it across.
We move your app off a framework that was a good idea at the time and onto a current one, while it keeps running. You stop paying a little more for every release.
A redesign used to mean a rebuild, which is why so many never happened. Now the new design goes through every screen, and nothing your users rely on goes missing.
Most businesses have work where capable people spend their days reading, sorting, checking and answering. We find where AI can take that on, build it, and tell you plainly where it can't.
SKAI gets you close to vibe coding speed while keeping your quality standards, so you build more and better software. The decisions that should be yours still come to you, at the right moment.
We know what finished takes, because we have built apps since 2015 for companies including Expedia Group, 7-Eleven, Experian and ZenBusiness.