AN Express
International money transfer app with secure onboarding, exchange rates, transaction tracking, and production mobile deployment for remittance workflows.
Flutter, iOS, Android, Web
Swift Development for Connected iOS Products
I am currently building native Swift apps alongside my mobile and full-stack work. These apps are not live yet. My published client portfolio remains Flutter-based, so native scope starts with a discussion of the actual code and requirements.
Discuss your Swift codebasePut the network boundary in focus
A useful starting point is one request and its lifecycle: decoding the response, representing errors, handling cancellation, and keeping credentials out of the client. Review the API contract alongside the Swift code rather than treat a decoding failure as an isolated UI issue.
Concurrency needs an ownership model
Decide which component owns each asynchronous task and what should happen when the user leaves the screen. Separate loading, cancellation, and failure in the product behavior. A modernization plan should explain which concrete bugs or maintenance costs it addresses.
Native work in progress
My current native applications are still being built. I will add an inspectable showcase when it is ready, with architecture notes and a demo. The iOS releases in the linked Flutter case studies provide mobile delivery context, not evidence of Swift implementation.
Related product work
Before we start
Is there a published native Swift case study yet?
Not yet. Native apps are in progress. Existing published client mobile case studies describe Flutter implementations.
Should Swift modernization include a UI rewrite?
Treat language, networking, and UI changes as separate decisions. Agree which problem each change solves before coupling them into one migration.