From the first idea to the store release: custom cross-platform apps built with Flutter – thoughtfully conceived, designed and technically implemented.
An app isn't automatically the best solution for every digital project. It becomes especially interesting when users interact with a product regularly, or when features are needed that go beyond a classic website.
Fast access directly from the smartphone and a more product-focused user experience.
Proactively inform users about new content, reminders or relevant events.
Make certain features and data available even without a permanent internet connection.
Integrate camera, GPS or other smartphone features into the product.
Enable personalized content, individual data and recurring usage.
Structure mobile processes that go beyond a simple website.
Make a digital product available as a standalone application via the Apple App Store and Google Play.
If a web app or responsive website makes more sense for a project, that should be part of the consultation too. I don't automatically recommend an app, but the technically and economically most sensible approach.
Which variant makes more sense depends on user behavior, required features, budget and long-term product goals.
Apps tailored to the specific product and requirements of the company.
A first working version of a product to validate idea, market and usage early.
New features, bug fixes and technical improvements to existing applications.
Implementing existing Figma screens cleanly, responsively and as pixel-accurately as possible.
Modernizing existing user interfaces and targeted UX improvements.
Connecting APIs, authentication, databases, external services and backend systems.
For many app projects I work with Flutter. This allows iOS and Android applications to be developed from a shared codebase.
Less duplicated work for iOS and Android.
Design and behavior can be controlled consistently across platforms.
New features and changes don't have to be developed completely separately.
Flutter is also well suited to more complex interfaces and production applications.
An offline app for project management and report creation. All data is stored locally. Users can document progress and export reports directly as PDF.
Contributed to a live app and PWA with feature development, bug fixes and ongoing design updates within an existing codebase.
Role: Development team member at Marqably
Ongoing development of a news app with hundreds of thousands of active users. Worked on bug fixes, feature extensions, dark mode and continuous design updates.
Clarify idea, target audience, feature scope, platforms and budget.
Structure user flows, features, navigation and technical requirements. We clarify which features truly belong in version 1 and which can be added later.
Define screens, components and interactions. If Figma designs already exist, they can be adopted.
Technical implementation of the app with regular test builds for early feedback.
Check functionality, devices, screen sizes and typical usage scenarios.
Preparation and publishing for the Apple App Store and Google Play.
New features, adjustments and maintenance after launch.
For new product ideas, not every planned feature needs to be built right away. An MVP focuses on the most important features that let the product be used and tested for real, for the first time.
The goal isn't to build as little as possible, but to build the features that are decisive for real-world use first.
Costs depend heavily on feature scope, design, backend, user accounts, integrations and platform requirements.
Scope
A small MVP with a few core features differs significantly from an extensive product platform.
Backend
A simple API requires different effort than a custom backend with complex business logic.
User Accounts
Login, roles, permissions and personalized content increase the feature scope.
Data
Local storage, cloud sync or complex data models influence the architecture.
Integrations
Payment, maps, external APIs or existing company systems can create additional requirements.
Offline Functionality
Local data and later synchronization require additional technical logic.
Design
An existing Figma design, or full concept and design work.
Platform & Release
iOS, Android as well as App Store and Play Store requirements.
After an initial consultation, the required scope can be structured and a realistic effort estimate created.
Get a Project EstimateApps keep evolving after launch. Operating systems change, user feedback comes in, and new features become relevant.
Existing apps can also be developed further step by step – either on a project basis or through ongoing support.
The specific technical setup depends on the product, requirements and existing system landscape.
Costs depend heavily on feature scope, design, backend, integrations and technical requirements. After an initial consultation, the required scope can be structured and a realistic effort estimate created.
That depends on the scope. A focused MVP can be built much faster than a complex platform with backend, user accounts and numerous integrations. A realistic project scope and timeline is defined at the start.
Yes. For many projects I work with Flutter, which lets me build iOS and Android applications from a shared codebase.
Not necessarily. With cross-platform technologies like Flutter, a large part of the application can be built together. Platform-specific adjustments may still be necessary.
Flutter is a framework for building applications for multiple platforms from a shared codebase. I use Flutter especially for iOS and Android projects.
Yes. For new product ideas, a focused first version with the most important features can be built first. The product can then be expanded strategically based on real usage and feedback.
Yes. Existing applications can also be developed further through new features, bug fixes, integrations or design updates.
Yes. Existing Figma screens can be technically implemented as design-to-code and integrated into an existing or new app.
Yes. Publishing can be considered and technically prepared as part of the project.
Not necessarily. Depending on usage, features and budget, a responsive website or web app may make more sense. This decision should be clarified before development begins.
Yes. Depending on the use case, data can be stored locally and certain features used even without a permanent internet connection. Pictolog PDF, for example, is designed as an offline application.
Tell me briefly what the application should do, who will use it and which features are already planned. Together we can clarify which technical approach makes sense.