I design the data model, sync strategy, and state flow before writing a single widget. Domain logic doesn't live in the UI layer.
I've owned complete product cycles — roadmap, architecture, QA, App Store deployment, and user onboarding. Engineering and product thinking, unified.
Bluetooth printing, GPS tagging, barcode scanning, biometrics, PDF generation, enterprise XML sync — I own the full hardware-to-cloud delivery chain.
The challenges most Flutter developers avoid — offline resilience, sync conflict resolution, multi-role ecosystems — are my core specialization.
Local-first data with SQLite/Drift, transactional integrity, queue-based mutation sync, and XML DATAPACKET enterprise exchange. Built for field teams operating at zero connectivity.
Designed and shipped paired apps serving distinct roles — Moody consumer + merchant, van sales field agent + admin. Shared backends, divergent UX, synchronized state.
Relational schemas for inventory, suppliers, clients, and debt. Atomic financial transactions, automated credit allocation, daily closing (Clôture) with cost-price-at-sale capture.
Activation key licensing, PIN + biometric authentication via local_auth, Firebase security rules, and secure local persistence for apps protecting sensitive financial data.
Bluetooth thermal printing, barcode/QR scanning, GPS geo-tagging, PDF generation — production integrations for field receipts, stock scanning, and delivery logging.
End-to-end mobile UX design for a Dubai/Algiers Web3 company — MPC wallet flows, NFT marketplace QA (minting, rentals, royalties), WalletConnect integration, and DeFi protocol UX analysis.
Four products built from scratch — each solving a different set of real-world mobile engineering constraints.
A Gen Z-first food delivery platform built around mood and personality. Two live apps — consumer and merchant — available on iOS (App Store) and Android (direct download via moody-food.com), connected by a shared Firebase backend with real-time order orchestration. Full product ownership: roadmap, architecture, development, QA, and deployment.
Field distribution teams operate in warehouses and remote delivery routes with zero reliable connectivity. They still need to track van stock, record every sale, manage client accounts, handle payments, and reconcile with the central desktop system — all before end of day.
Retail and wholesale stores suffer three persistent problems: inventory mismatches from unrecorded sales, slow error-prone daily cash closing, and shared devices with no real access control. This system was built to solve all three — entirely offline, zero cloud dependency.
Fleet managers needed cloud visibility across multiple vans in near-real-time — while still tolerating the same unreliable field connectivity. Solution: local SQLite as source of truth, Firebase syncing opportunistically when connectivity permits.
I design mobile systems the way backend engineers design services — explicit boundaries, predictable state, and data models built for the constraints that actually exist in the field.
Presentation → Domain → Data. UI that knows nothing about storage. Business logic that knows nothing about Flutter widgets.
Order lifecycles, sync queues, and financial workflows modelled as explicit state machines — no hidden transitions, no impossible states.
Entities designed for sync from day one: transactional mutations, conflict strategies baked into the schema, and audit trails for financial data.
Biometric gates, activation licensing, Firebase security rules, and encrypted local persistence — first-class requirements, not afterthoughts.
/// Daily Clôture — captures cost price at /// time of sale for accurate daily P&L. /// Atomic: no partial closes allowed. class DailyClosingService { final SalesDao _sales; final InventoryDao _inventory; final Database _db; Future<ClosureResult> executeClôture({ required DateTime closingDate, }) async { return _db.transaction((txn) async { final sales = await _sales .getUnclosed(date: closingDate, txn: txn); double turnover = 0, cogs = 0; for (final sale in sales) { // Cost captured AT TIME OF SALE final cost = await _inventory .getCostAtDate( productId: sale.productId, date: sale.saleDate, txn: txn, ); turnover += sale.price * sale.qty; cogs += cost * sale.qty; await _sales.markClosed(sale.id, txn: txn); } return ClosureResult( turnover: turnover, costOfGoods: cogs, grossMargin: turnover - cogs, closedAt: DateTime.now(), ); }); } }
Every item below has shipped in a real system.
Unsolicited feedback from users, restaurant owners, and business clients across all three products.
I just discovered this and I can't begin to describe how grateful I felt to finally see a business like this here in Médéa. The concept is incredibly creative and the app itself is beautifully designed and thoughtfully made.
The app is very useful and professional. It genuinely helps a lot — I'm really happy that something like this is finally available in our city.
This app has been a real game changer for my restaurant. I can now accept orders instantly without having to answer the phone for every single request.
I use this app in my store every single day. It's completely changed how I manage my business — I can now instantly see what I've sold, how many items are left in stock, and calculate my profit at any time.
The app is simple and easy to use — nothing like the complex systems we had before. I can load the vans, check stock levels, add new clients, and start selling right away. Exactly what we needed in the field.
I'm a Flutter developer based in Algiers with a Master's degree in Fundamental Informatics & IT from RUDN Moscow. I build mobile systems — not just mobile apps.
The distinction matters. An app displays information. A system runs an operation. The van distribution system I built processes thousands of financial transactions entirely offline. The Stock Manager enforces atomic inventory and credit logic that accountants depend on daily. Moody is a dual-sided marketplace — two apps, one backend — live on the App Store right now.
My background spans Flutter engineering, product ownership, and blockchain/Web3 — which means I bring full-stack thinking to every project. I understand backend constraints, database design, and API contracts well enough to build systems that work end-to-end.
Open to freelance projects, remote full-time positions, and on-site roles — and willing to relocate if the opportunity is the right fit. Particularly interested in logistics, field operations, local commerce, and any domain where mobile needs to work under real-world constraints.
I take on a small number of projects so I can give each one the engineering attention it
deserves. If you're building something with real constraints — let's talk.
📍
Algiers, Algeria · GMT+1 · Usually responds within 24h
