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.
I’m Mirza Karić, a Senior Flutter Developer building production-ready applications for iOS, Android, and Web. I work across architecture, implementation, integrations, and the production details that keep products reliable as they evolve.
- Role
- Senior Flutter Developer
- Delivery
- iOS · Android · Web
- Focus
- Clean architecture
- Based in
- Bosnia & Herzegovina · Remote
What I bring
Flutter ownership across the product lifecycle.
I connect product requirements with technical decisions, then carry the work 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
How I work
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.
Next