Web, SaaS and mobile applications
We design and build SaaS platforms, customer portals and admin panels, as well as iOS and Android apps — from architecture to app-store release.
- 01Java and Kotlin with Spring Boot — backends and APIs
- 02Next.js, React, TypeScript
- 03React Native (Expo), Supabase, PostGIS
- 04OAuth2, MFA, roles and permissions
- 05Subscriptions, payments, push notifications
A good application is more than an interface. It is a data model that survives five years of change, permissions you can explain to an auditor, and an admin panel the team actually wants to work in.
What we do
- SaaS platforms — backends most often in Java or Kotlin on Spring Boot (Node.js too), Next.js frontends. OAuth2 with MFA, billing, coupons, customer-facing APIs.
- Customer portals and admin panels — interfaces where customers manage their accounts and the team runs sales, support and processes. We build them so that the next internal tool is another tab, not another application.
- Mobile applications — React Native (Expo) for iOS and Android: maps, geolocation, push notifications, in-app purchases, multiple languages. We take the app through the whole App Store and Google Play release process.
- Backends for apps — Supabase or a custom API, PostgreSQL with PostGIS, serverless functions, end-to-end tests.
How we work
Short iterations with a working test environment from week one. Every change goes through a pipeline with tests — including mobile apps, where end-to-end tests protect against regressions that cannot be rolled back quickly.
Related case studies
- Industry
- Own product — mobile app for sailors
- Timeline
- 2 months (May–Jun 2026)
- platforms from one codebase
- 2
- languages
- 7
Sea Spotter — a mobile app for reporting marine wildlife sightings
Our own product. Sailors report marine wildlife sightings — dolphins, whales, orcas and more — and the app turns them into an activity map and alerts others nearby. iOS and Android, multiple languages, subscriptions, AI-powered species-name translation.
Read the case study
- Industry
- SaaS — automotive intelligence (US)
- environments — test, beta, canary, production
- 4
- automated tests in the modernised service
- 0 → 200+
Modernising a SaaS platform — from a decade-old application server to full DevOps
An automotive data platform for the US market ran on an application server more than a decade old and was built by hand. We moved it to a modern stack, built new interfaces for customers and staff, and a complete CI/CD process on our own Kubernetes cluster.
Read the case study
Planning a SaaS platform or a mobile app?
Tell us who it is for and what it should do. We will propose an architecture and a plan — with app-store publication scheduled as a stage of its own, not an afterthought.