Services

1. What I do

• Mobile apps, start to finish From idea to a release on the App Store and Google Play. Product decisions, the app itself, the backend behind it, and the store review that stands between you and shipping. Solo, or inside a team that already exists.
• Ad-hoc engineering support Extra engineering hands for software houses and companies that need to hit the ground running. I join an existing codebase, work to your conventions, and pick up a scope rather than a rewrite.
• Backend & infrastructure APIs, databases and deployments that survive the night. Spring Boot and PostgreSQL behind a REST API, containerised, on a Linux VPS — with nightly backups and a restore command that has actually been tested.
• Integrations Talking to systems that were not built to be talked to: Microsoft Intune, Firebase, Bluetooth Low Energy and IoT hardware, social sign-in, analytics, AI image analysis, and native platform code bridged into Flutter in both directions.

2. Work other people left behind

A fair share of what comes in is a project someone else started.

• Rescue & takeover Apps whose developer moved on, projects left half-finished, and migrations off no-code platforms onto something that can be maintained. The first job is usually working out what is actually there.
• Store presence Apple and Google review problems, appeals, and keeping a listing live and current — including the rejections that are about policy rather than code.
• Awkward cases A PWA instead of a native app, restricted industries, integrations the store guidelines do not have a category for. The cases that get a "no" elsewhere.

3. How it works

• Direct communication with the person writing the code — no account layer.
• EU timezone (Poland), working in English or Polish.
• Scope can be a fixed piece of work or an ongoing arrangement; both start with a conversation about what has to be true when it is done.

4. Contact

Happy to talk through whatever you're up against — including the parts you are not sure are possible.