Software studio Prague
Your product in your customers’ pockets.
We build digital products around apps.
The app is what people see. Beneath it we build everything that holds it up: the web app and admin, the connection to your API, security and release.
Before you commit, we show you a short concept of the app, free of charge.
- Designed after the world’s best apps
- Security planned from the first line of code
- Just as good on iPhone and Android
Product layers01 / 06
Mobile app. The main layer. iOS and Android in one codebase: React Native, Expo, TypeScript.
On screen: Hospital management system, Plan and actual · sample data
Services
Mobile apps for new and existing products.
Tolaron is a Prague software studio focused on mobile apps. We build apps for iOS and Android and web apps, alongside a mobile app or on their own, mainly for healthcare, energy, logistics and fintech.
The whole platform, from one team
We design and build the whole platform: the client portal your customers sign in to, the iOS and Android app, and the admin your team runs it from. They are built together, so they work as one product. What the platform needs on the server side is agreed in the project scope.
Best fit: a new product your customers will use on the web and on their phones.
One direct contact. From the first meeting to release, you deal directly with Zdeněk Dolák, who leads development.
Scope and budget in writing, up front. We agree the scope of work and the budget cap in writing before we start. Any increase in the budget always needs your approval.
Case studies
Apps for fintech, compliance and insurance.
Founder’s freelance experience
Five years building fintech apps.
Zdeněk Dolák spent five years leading mobile development for a UK FCA-authorised payment institution: KYC, KYB, onboarding, document e-signing, a dashboard app and a POS app. His freelance experience now informs every Tolaron project.
- KYC
- KYB
- Onboarding
- E-signatures
- Dashboards
- POS
Sectors
Apps for healthcare, energy, logistics and fintech.
01Fintech
Systems where payment is the app’s main purpose. The founder brings experience in payments, compliance and onboarding from the UK.
Revolut · example from Mobbin 02Healthcare
Sensitive data, procurement rules and people with no time for software. It has to be simple, and it has to be up.
CVS Health · example from Mobbin 03Energy
Usage in kWh and in money, the number first and the chart after, and clarity even when the data is not up to date yet.
Octopus Energy · example from Mobbin 04Logistics
Delivery time first, a clear view of how the delivery is going and help one tap away, even when it runs late.
Grab · example from Mobbin
…or anywhere money is at stake.
How we design apps
We know what works.
Our strength is fintech apps and screens full of data. Using apps that do it well, we show why a particular solution works. We put the same principles into your design.
Strength 01
Fintech apps
Payments, cards, onboarding and KYC. For five years the founder led fintech app development in the UK.
Strength 02
Data and dashboards
Overviews, charts and numbers people understand at a glance, on the phone and on the web.
ExampleThe screens are examples from other companies’ apps (the Mobbin library), not our work. They show the principles we design by.
Fintech · Payments without surprises
A transfer check people actually read.
Revolut, transfer review. Hover over the numbers.Revolut, transfer review. Tap the numbers.
1Why it works
A check for a new payee
Before sending, Revolut asks whether you know the payee. The warning sits above the amount, so it cannot be missed.
In our design: A first payment to a new account gets a reminder to check the recipient, giving people a chance to reconsider the transfer.
More fintech screens that work · hover over a screentap a screen
The examples are other companies’ apps from the Mobbin library (Revolut, Wise, Lloyds, Cash App, Monzo, CVS Health, Warby Parker, Zocdoc, Wonder, Bolt Food, DoorDash, Octopus Energy, Amplitude). They are not our work; they show the principles we design by. Names and trademarks belong to their owners. Tolaron’s samples use made-up data.
Explore our design processApproach
How an app project runs.
Project overview · Your app
SampleBefore development
- Users and their main task
- Systems the app connects to
- Unknowns, named together
In writing: scope, responsibilities, acceptance criteria and the estimate
Short concept · freeThroughout
Sample. We bill only the time we actually work.
When something changes, you decide before we spend more.
After release
- What to trackwe agree
- Who receives alertswe agree
- How issues are handledwe agree
Monitoring such as Sentry, if we include it.
Discovery
We check that working together makes sense for both sides, and we can show you, free of charge, a short concept of roughly what the app could look like.
Backend
We build on the API you have. When it needs to change, we work with the person on your side who can change it.
People
Zdeněk leads the project, is your contact and stays responsible for delivery. Specialist roles are agreed for your project.
Billing
We bill the time we actually work, under a cap agreed up front.
After launch
We agree maintenance, support and incident responsibilities for your project.
Security and continuity
- Accounts and keys
- Who owns the code, the App Store and Google Play accounts and the signing keys is written into the agreement before work starts.
- Updates
- Dependencies are kept up to date with automated update checks, and every change passes automated tests before it ships.
- In production
- Before launch we agree how production errors are reported and who receives the alerts.
- Continuity
- Code, decisions and release steps are documented in the project’s repository, so the project never depends on one person’s memory.
FAQ
Questions before an app project.
Scope, dependencies and the practical details of working together.
What should we send in a project enquiry?
Tell us who will use the app, what they need to do and which system it should connect to. Include the current app or API if one exists, your priorities and any timing constraints.
How do you estimate and charge for the work?
We estimate against an agreed scope and bill actual work under an agreed budget cap. Cost depends on the user journeys, design, API readiness, integrations and testing. Changes that need more budget require agreement before the extra work.
Do we need an existing backend?
For an app on a product you already have, the best start is a working API and someone on your side who can change it. For a new product built around the app, what it needs on the server side is agreed as part of the scope. Backend development is not a standard service: where a project needs it, we discuss it for that project.
What needs to be agreed before work starts?
The scope, responsibilities, dependencies, acceptance criteria and estimate. Code ownership, store accounts, release responsibilities and maintenance terms also need to be settled in the project agreement.
Who will we work with?
Tolaron is led by its founder, Zdeněk Dolák, who is your contact for the project. Other developers join as capacity is planned, but we deliver an agreed product scope, not developer capacity.
Can we work together remotely?
We serve Czech and international clients in Czech and English from Prague. Tell us where your team works so we can agree communication, decision-makers and meeting times.
Something else? Write to hello@tolaron.com or book a 30-minute call.
Tell us about your project and what the app needs to do.
- Who will use the app
- What they need to do in it
- Which system it connects to
- Priorities and any deadline
Zdeněk Dolák, founder