Complete products
The app, the backend and the website, built to fit.
I build complete products: the backend and database, the admin, the website and the mobile app. One person holds the whole picture, so the data model, the payments and the releases agree with each other.
- Web interface
- Mobile app
- API & logic
- Database
Recent full-stack work
In 2026 I built both halves of meinunfallauto, an EU automotive commerce platform: a Laravel 12 backend with admin and partner dashboards, and a Next.js 16 customer site in German, English and Arabic (right-to-left).
- Stripe reservation deposits tied to inventory holds, with retry-safe webhooks and real refunds.
- A domain-specific search engine with its own lexicon and query parser.
- A legacy database import over a read-only connection.
- An in-admin CMS with a cached content API that refreshes when the data changes.
- Paguely, my own product: Flutter app, Supabase backend with 24 migrations and 13 edge functions, RevenueCat subscriptions.
What is included
A complete product includes everything a user, an operator and a payment provider touch.
Product definition
Your brief becomes a written scope: roles, user paths, data, payments, what the first release leaves out.
Backend and data
Supabase (Postgres, row-level security, edge functions), Firebase, Laravel or Node, chosen for your team and budget, with migrations in version control.
Admin and operations
Dashboards for your staff and partners, roles and two-factor sign-in, invoices, background jobs, content editing without a developer.
Website and web app
Next.js with server rendering where search matters, several languages including right-to-left, forms that validate on both sides.
Mobile app
A Flutter app on the same backend and the same rules, released to both stores.
Payments
Stripe checkout, deposits, refunds and webhooks that survive retries; store subscriptions where the app needs them.
How a product gets built
The product gets built from the data model outwards, and a user can walk through it end to end before features are added.
Scope and data model
Who uses it, what they do, what is stored and who may see it.
Walking skeleton
Sign-up, the main action and a payment working across backend, web and app.
Features in slices
Each slice goes through every layer at once, with tests, so nothing waits on another team.
Launch
Hosting, domains, email, monitoring and store release, with a short handover document.
Questions
Can one engineer build the whole product?
For a first release of a focused product, yes. I build the backend, admin, website and app myself, which removes the hand-offs where most delays start. For larger scopes I say early what needs more people.
Which backend do you use?
Supabase, Firebase, Laravel or Node, depending on the product and who maintains it later. I explain the choice in the scope before any code is written.
Do I own the code and the accounts?
Yes. The code lives in your repository and the hosting, store and payment accounts are yours. I work inside them.
Can you build a multilingual site?
Yes. I have shipped products in English, German, Bosnian, Hungarian and Arabic, including right-to-left layouts.
Can you continue a product started in a no-code or AI builder?
Yes. I have taken over a product begun in Lovable and moved it toward a store release. I start by checking the data model and security rules.
What happens after launch?
I can stay on for fixes and new features, or hand over with documentation and a walkthrough for your team.
Have a product to build from scratch?
CS-01Describe who uses it, what they do and what they pay for.
- What the product does and who uses it.
- What exists already: designs, code, a backend, a store account.
- Your deadline, and anything fixed such as a launch date or a platform.