Wear It
Authenticated luxury fashion marketplace connecting buyers and sellers: catalogs, multi-role workflows, payments, orders, and logistics across Flutter for iOS, Android, and web.
Flutter, iOS, Android, Web
Flutter + Laravel Development Without the Mobile/Backend Handoff
I work across Flutter and Laravel so mobile behavior can be traced through the API, authorization, and stored data. That is useful when both teams see a different half of the same bug.
Discuss your Flutter and Laravel productStart with the request that failed
Compare the app’s request with validation, controller behavior, serialization, and authorization. Distinguish an expired session from a permission failure. Make error responses useful to the app without exposing internal details.
Account for work that finishes later
Queues, payment webhooks, and third-party APIs can complete after the app receives its first response. Define pending, completed, and failed states, including how the user recovers. Repeated requests should not accidentally create duplicate business actions.
Release both sides deliberately
An API change can affect installed clients that have not updated. Review compatibility, database migrations, and rollout order. Marketplace and remittance projects in my portfolio illustrate the types of connected workflows involved; their cards do not claim a Laravel backend unless documented.
Related product work
AN Express
International money transfer app with secure onboarding, exchange rates, transaction tracking, and production mobile deployment for remittance workflows.
Flutter, iOS, Android, Web
Before we start
Can the mobile app be fixed without changing the API?
Sometimes. Compare the expected contract with the actual response first. A client workaround can hide a server fault, while an API change can affect other consumers.