Structure you can see · illustrationERIKSLAIER Build
Build
Code you can hand over
Mobile apps, web apps and logic-heavy sites. We build in short stretches and show results you can open, not a slide about progress.
Mobile
iOS and Android. We choose native or cross-platform by requirements, not habit. We think about offline, notifications, OS updates and how the app behaves a year from now.
- new apps and new features
- migration to new OS versions
- stability and failure handling
Web
Account areas, internal panels, interactive site parts. Accessibility and speed are part of the job, not “later”. Forms keep input; errors explain what to do.
- responsive UIs at 390–1440 px
- integration with existing services
- teardown and repair of old code

Code another team can take over without us is the main test of good engineering.
ERIKSLAIER
What to choose: a cheat sheet
Not an answer for every case, but a starting point for a conversation.
| Approach | Strength / cost | When it fits |
|---|---|---|
| Native iOS / Android | Full platform capability; two codebases | Complex gestures, hardware access |
| Cross-platform | One codebase; some limits | Most business apps |
| Web app | No stores, instant updates | Dashboards, internal tools |
| Responsive site | Easiest to maintain | When an app isn’t justified |
Inherited code
The previous developer left, there are no docs, and the app is needed tomorrow. A familiar story. We start with a teardown of a few days: run the project, map the modules, flag risks — and only then propose a plan.
What you get after a teardown
- a state report: what’s stable, what’s fragile
- a list of risks with explanations
- options: fix, extend, rewrite a part
- an estimate range for each option