Systems designed to change
Clean boundaries, predictable state, and explicit data flow keep Flutter applications understandable as features and teams grow.
Open to full-time and contract Flutter roles
Flutter products built for the long run.
Flutter development for iOS, Android, and Web, focused on clean architecture, reliable integrations, performance, and maintainable code.
- Role
- Flutter Developer
- Delivery
- iOS · Android · Web
- Focus
- Clean architecture
- Based in
- Bosnia & Herzegovina · Remote
Engineering scope
Flutter ownership across the product lifecycle.
The work connects product requirements with technical decisions, then carries them through implementation, integration, release, and continued improvement.
Cross-platform delivery with judgment
Shared Flutter foundations are balanced with the interaction, lifecycle, and release expectations of each target platform.
Production behavior considered early
Performance, failure paths, recovery, integrations, and maintainability are treated as part of delivery rather than work left for later.
Selected work
Engineering decisions, not logo walls.
Concise case studies about structure, constraints, and the reasoning behind dependable cross-platform products.
01Independent technical case study
Creator & Flutter Developer
MultiBook
A private marketplace built as a production-oriented Flutter application for iOS and Android, supported by a Go API, PostgreSQL, and selected Firebase services.
View case study
02Social discovery mobile application
Flutter Developer
PinTreats
A Flutter social discovery app that helps people find places to eat, share food experiences, connect with others, and keep track of memorable locations.
View case study
03Digital health mobile application
Flutter Developer
Univa
A Flutter digital care application supporting people with eating disorders and the families who care for them through guided programmes, daily tools, reflection, and connected progress.
View case study
Client feedback
Trusted when Flutter work gets demanding.
Direct feedback on work involving existing products, complex delivery, and the quality of the code left behind.
“He quickly understood the existing codebase and successfully refactored the entire application. Mirza is reliable, detail-oriented, and communicates clearly.”
“Demonstrated strong expertise in Flutter, delivering clean, well-structured, and scalable code. Communication was smooth and proactive, and challenges were handled with a solution-oriented mindset.”
Working principles
Calm systems. Explicit trade-offs. Useful software.
Product before patterns
Architecture earns its place by making real product work safer and easier to change.
Native where it matters
Shared code should support each platform’s expectations, not erase their differences.
Quality in the loop
Accessibility, failure states, reviewability, and release confidence shape delivery from the start.
Start a conversation
Building or improving a Flutter product?
New build or existing codebase, the conversation can start with the product, its constraints, and what needs to improve.