On every SSB software product
Flat 30% discount on any software
School, hospital, hotel, restaurant, HR, lab, pharma and the rest of our software. Ask for a quote and we apply 30% on the price. Write to info@ssbconsultancy.com.
A mobile app is the right shape when the person is away from a desk: a driver, a parent, a site engineer, a member at the door. It is the wrong shape when a phone website would do the same job with less to maintain.
Apps are often commissioned because a competitor has one. The first version then includes every screen from a template. Users open it once, wait, and go back to WhatsApp, which was faster.
We ask where the person is standing when they need the tool. If they are at a desk, a website is usually enough. If they are at a gate, a site or in a vehicle, the phone app earns its cost.
The first build is that moment. Login, the action, and a result the office can see. Store listings, extra languages and offline mode are added when the first action is used.
The thing the user opened the phone to do
Tried on a slow connection, not only on office Wi-Fi
The user sees their job, not a sample account
Play Store or App Store only if you will keep the listing
The app is commissioned to match a competitor, without a job only a phone can do.
The first version is a catalogue of screens nobody finishes.
It is tested on a new phone in the office and fails on a cheap Android outside.
Accounts are shared, so nobody knows who confirmed the action.
The store listing is treated as the product, and then nobody updates it.
We say if a website is enough. An app is scoped only when the phone is the point.
Version one is one action and the office result.
We check it on a modest Android and a slow connection before calling it done.
Each user has their own login.
A store release is a milestone with a named owner on your side for the account.
Decide from where the user stands. This step is allowed to end in “do not build an app”.
One job, one result, sample data from you.
Not the newest device in the room. Fix what fails there before new screens.
If you want a listing, your account and the update owner are part of that milestone.
When both audiences are real. If your users are on Android, we do not spend the first release on an iPhone build nobody will install. The quote says which.
Only if the job requires it, and only for the data we agree to store on the phone. Offline is a scope item. It is not assumed.
You do. We should not be the only people who can update your app. That is part of handover.
Describe the one action and who does it away from a desk. A price for “an app like that other app” is not a brief.
A seat, a room or a cab is promised on WhatsApp and again on a call. A travel app keeps one availability and one booking.
A polished layout that staff cannot finish a task on. UX here is the path of the real job, tested before it is built.
The project starts from a paragraph and grows in chat. A custom software engagement writes the first release, the price and the milestone you can click.
Tell us the operation that is breaking. We will walk that screen and send a written quote.
We reply instantly
