Mobile apps

• iOS and Android from one codebase.React Native and Expo, with native modules only where they are needed, such as Face ID sign-in or a barcode on the screen.
• Offline that actually works.A local cache for what people need at the moment of use, clear states when something is stale, and sync when the connection comes back.
• Logic shared with the web.Validation and business rules live in one shared package used by the app, the web and the API, so they cannot drift apart.
• White-label when you need it.One app that each customer company sees in its own branding, with only the modules it pays for switched on.
• The backend too.The API, the admin for your team and the push notifications, so you have one person responsible for the whole thing.

• FirmFlowA white-label employee app: the week’s menu, one-tap ordering and a barcode card at the counter, offline and with Face ID. Expo, React Native and a Symfony 8 API, 590+ tests. Preparing the first release. Read the case study
• FyzioDeskThe client-facing mobile app of my physiotherapy SaaS, sharing its rules with the web app through one package. In progress. Read the case study

1. A call about who uses the app, where, and what they must be able to do without signal.
2. A clickable prototype on your phone early, through Expo, before anything is final.
3. A fixed price for the first release, or a monthly retainer.
4. App Store and Google Play submission, then updates over the air where the stores allow it.

From €70 per hour, or a fixed price for the first release once the scope is clear.

I work remotely from Nitra, Slovakia, in the CET time zone, in English. Working hours overlap fully with the UK and the rest of Europe, and with US East Coast mornings. You get one person from the first call to launch, progress you can click on a staging server every week, and invoices from an EU company with VAT reverse charge for business clients.

• PrestaShop developer
• Web apps and SaaS
• Websites
• Online stores