Challenge
NKM needed separate mobile surfaces for shoppers, full admins, and catalog staff — each with different permissions, without exposing order or customer data to the wrong roles.
mobile · 2025
Three Flutter apps for NKM B2C — consumer shopping app, full admin APK, and staff catalog management app.

Overview
NKM's B2C mobile suite spans a consumer Flutter shopping app, an admin-only APK for orders/revenue/notifications, and a staff catalog app for categories, sub-categories, and design uploads — all connected to the B2C Laravel API.
Challenge
NKM needed separate mobile surfaces for shoppers, full admins, and catalog staff — each with different permissions, without exposing order or customer data to the wrong roles.
Strategy
Build role-specific Flutter APKs with API-level enforcement: admin APK for operations, staff APK for catalog only, and a consumer app for mobile shopping.
Solution
Admin APK with dashboard stats, order approve/cancel, customer list, and push notifications; staff app for category/sub-category/design CRUD; consumer Flutter app with prod/dev flavors for gold jewellery browsing.
UX note
Priority was given to readable hierarchies, status visibility, and journeys that support busy users — not decorative complexity.
Technology
Process
Features
Results
Architecture
Visuals
Selected visuals from the delivery set, used to communicate product direction and interaction density.

Screen 01
NKM B2C Mobile Suite

Screen 02
NKM B2C Mobile Suite

Screen 03
NKM B2C Mobile Suite
Testimonial
Feedback from the team we built this project with.
“Having separate admin and staff mobile apps means our team can approve orders and manage the catalog without being tied to a desktop. Push alerts for new orders are especially useful.”
Related projects
Next step
Share your industry context and goals — we'll help frame scope, UX priorities, and architecture.