# Nimr Sawafta | Flutter & Mobile App Developer in Casablanca, Morocco > Experienced Flutter developer, senior mobile app developer and app publisher in Casablanca, Morocco. Tech lead and freelance IT consultant building, launching and publishing apps across Casablanca, Morocco and North Africa. I turn problems into products with a clear path to market—bringing together thoughtful design, scalable code and the people needed to build them. ## The work behind the title. Senior Tech Lead at Walycash. Based in Casablanca, Morocco. Open to freelance projects and recruitment conversations across Morocco, North Africa and beyond. I take ownership of difficult problems, unblock teams and turn business needs into products people can use. My leadership has ranged from small teams of three to an Enactus team of 200. ### A career built by shipping - 2019 · First store release: Released my first app to app stores with Les Petits Amies in Portugal, followed by My Essouria and La Route des Empires in Morocco, working with the state and the French embassy. - Early leadership: Built the Maroc24 app and led engineering; led a team at Enactus. At Harmony Technology, I worked on Adala. - Product delivery: Led mobile development at Ticket.ma, creating a new stack, app, ticketing systems and scanners. Built eSimply at Nuitée and worked on the Prestigia mobile app. - Technical leadership: Led the start of Yakeey Pro’s refactoring; at Tech for Palestine, led work including the Jaywalk migration. Now Senior Tech Lead at Walycash, rebuilding legacy apps with new code and interfaces. - Independent work: Freelance work includes Yool, ICON and Laundry Service. ### How I make technical decisions - Start with the business: Choose technology for the problem. Use Flutter for cross-platform apps where it fits, with Go, Node.js or Python for backend services when appropriate. - Make change sustainable: Organize features around domains with clear shared interfaces, shared design-system packages and a single source of truth. Model business and technical states explicitly instead of multiplying flags. - Build for the whole operation: Pair polished user experiences with maintainable code and administrative tools where needed, so teams can operate and evolve the product. - Release with care: Use automated and unit tests, deployment pipelines and pre-production testing. I also use AI-assisted audits to look for missed errors and unwanted code. ## The work in context ### [ticketma](https://nimr-sawafta.web.app/en/companies/ticketma/) - My role: Lead mobile app developer - The challenge: Support event booking and the operational work at venue entrances. - What I did: Led mobile development and built the booking app, plus tools for generating badges, controlling gates and scanning tickets. - What it delivered: An event-booking app alongside tools for managing event access. ### [laundry-service](https://nimr-sawafta.web.app/en/companies/laundry-service/) - My role: Freelance software developer - The challenge: Support day-to-day operations across laundry stores. - What I did: Built an ERP system and a point-of-sale app for managing stores and registering orders. - What it delivered: Tools for store management and order registration at the point of sale. ### [nuitee](https://nimr-sawafta.web.app/en/companies/nuitee/) - My role: Lead mobile app developer and sole developer of eSimply - The challenge: Turn travel connectivity into a usable mobile product. - What I did: Built eSimply from idea through release, developing the app for purchasing travel eSIMs. - What it delivered: A released travel app for choosing, activating and managing eSIM data plans. ### [prestigia](https://nimr-sawafta.web.app/en/companies/prestigia/) - My role: Lead mobile app developer - The challenge: Move a legacy hotel-booking app toward a new cross-platform experience. - What I did: Worked on the migration and built the mobile interface with Flutter, focusing on a polished booking experience. - What it delivered: A new mobile booking experience built on a cross-platform foundation. ## Product strategy & release: From problem to product. Since 2017, I’ve helped turn problems into products and build a path to market. I’m a hands-on leader: when things stall, I bring clarity, move the work forward and help the team get it done. 1. Define the problem 2. Explore and design solutions 3. Test and validate 4. Build the product 5. Launch and improve ## What I can build. From the first screen to the systems behind it. I build UX-first platforms, modernise what already exists, and lead the teams that deliver them, for clients across Casablanca and Morocco, Palestine, North Africa, the Arab world and beyond, in English and Arabic. ### [Mobile applications](https://nimr-sawafta.web.app/en/services/mobile-applications/) Fast, reliable iOS and Android apps built with Flutter by an experienced mobile developer in Casablanca, with smooth interactions and experiences people enjoy coming back to. From first tap to five stars. A mobile app lives in someone’s pocket: used in a hurry, with one thumb, on a weak connection. I design for that moment first. 1. Follow the thumb: With the team, I watch how people really hold, tap, and abandon the app, and find the exact moments where they hesitate. 2. Design the three-second path: Every key task gets a path a new user understands in seconds, with motion that explains rather than decorates, true to the product’s design. 3. One feature, one domain: Login, checkout, feed: each feature owns its domain, state, and code, over a shared core. New features land without breaking old ones. 4. Measure and improve: Crash-free sessions, launch time, and store reviews help the team understand where to improve. ### [Websites & web applications](https://nimr-sawafta.web.app/en/services/web-applications/) Distinctive websites, capable web apps, and backoffice tools. Built to load quickly, scale with your needs, and make everyday tasks easier. Fast to load. Obvious to use. On the web, people decide in seconds whether to stay. Speed and clarity are not features; they are the design. 1. Start from the jobs, not the pages: Together we list what visitors and operators actually come to do, and agree on the few journeys that matter most. 2. Design for the busiest user: Backoffice tools are shaped for the person doing the task two hundred times a day: fewer clicks, clear states, nothing to guess. 3. Domains, not folders of pages: Orders, users, billing: each business domain has its own logic and API over a shared core, so the product grows without tangling. 4. Ship light, stay light: Performance budgets, accessibility, and SEO are built into the first release and checked on every deploy after it. ### [Desktop & smart systems](https://nimr-sawafta.web.app/en/services/desktop-smart-systems/) Desktop software, connected devices, and IoT systems that bring your hardware, data, and operations together. Where software meets the real world. When hardware, people, and data meet, the hardest part is making it feel simple to the person on the floor. 1. Walk the floor: I learn the operation where it happens: the devices, the operators, the noise, and every point where things fail. 2. Design for a glance: Screens that read in a second and work under pressure, with clear feedback the moment a device goes quiet. 3. Every device behind a contract: Hardware integration, data collection, and business rules live in separate domains, so changing a device never means rewriting the product. 4. Built to survive offline: Local-first data, safe retries, and monitoring keep the system working when the network does not. ### [UI/UX & user experience](https://nimr-sawafta.web.app/en/services/ui-ux-design/) Interfaces and flows shaped around real users: fast, easy to understand, and consistent with your design system, from first sketch to polished screens. Design the brain can read. Great UX is invisible: people simply understand. My work is to make the complex feel obvious, without losing the soul of the product. 1. Listen before drawing: Interviews, analytics, and support tickets show where users get lost. The team agrees on the problem before anyone opens a design tool. 2. Sketch many, keep one: We explore several directions together and test them with real users. The simplest one that truly solves the problem wins. 3. A system, not a pile of screens: Tokens, components, and patterns become a design system that developers build exactly, and AI tools can follow just as precisely. 4. Motion with meaning: Animation only explains: where something came from, what just changed, and what to do next. ### [Legacy systems, modern foundations](https://nimr-sawafta.web.app/en/services/legacy-modernization/) Thoughtful migration from ageing software to maintainable, modern systems, with clean APIs and structured data ready for AI integrations. Modernise without stopping the business. The old system pays the bills today. The migration respects that, moving in deliberate stages instead of one risky rewrite. 1. Read the old system: Before touching anything, I map what the legacy really does, including the unwritten rules users depend on every day. 2. Stabilise the legacy: Fix what breaks, add tests and monitoring, and open clean seams so new features can sit on top of it easily. 3. Build the new, fast: New features and migrated modules are written in the new architecture from day one, domain by domain, with AI-assisted development keeping the pace high. 4. Stabilise the new, retire the old: Each migrated domain is hardened, measured, and adopted before the next one starts, until the legacy can be switched off safely. ### [Technical leadership & engineering management](https://nimr-sawafta.web.app/en/services/technical-leadership/) Leading developers as a senior tech lead and engineering manager: setting technical direction, growing engineers, removing blockers, and shipping on time. Teams that ship, and enjoy it. Great software comes from teams that understand the problem, trust each other, and know exactly what to build next. 1. One problem, one team: Engineers, designers, and product start from the same user problem, so the best solution comes from the whole team, not one voice. 2. Ownership by domain: Each squad owns its domains end to end, from code to quality to delivery, while everyone cares for the shared core together. 3. Clear the road: Blocked tickets, vague specs, slow reviews: my job is to remove friction so engineers spend their days building. 4. AI in the workflow: AI-friendly code, conventions, and review habits let the team move faster without lowering the bar. ## Pages - [Nimr Sawafta — home](https://nimr-sawafta.web.app/en/) - [Selected work](https://nimr-sawafta.web.app/en/projects/) - [The story](https://nimr-sawafta.web.app/en/story/) - [Technologies](https://nimr-sawafta.web.app/en/technologies/) ## Languages - [en](https://nimr-sawafta.web.app/en/llms.txt) - [ar](https://nimr-sawafta.web.app/ar/llms.txt) - [fr](https://nimr-sawafta.web.app/fr/llms.txt) - [es](https://nimr-sawafta.web.app/es/llms.txt) ## Contact - Email: nimr.h.sawafta@gmail.com - LinkedIn: https://www.linkedin.com/in/nimr-sawafta/ - GitHub: https://github.com/nimr77 - SudumTech: https://sudumtech.com/ - API (OpenAPI): https://us-central1-sudumtech-40220.cloudfunctions.net/api/openapi.json