Manufacturing / field ops · 2026 · iOS + Android
EuroDoor
Field operations for a door manufacturer — orders, site measure, and technicians. A work app, not a catalogue.
Technical Product Owner + Mobile Engineer
Field teams
Orders on the phone
Site measure
Visits from the app
Technicians
Updates from site
Click any screen to zoom
01
Context
EuroDoor is not a D2C furniture browser. It is the work app: sign in with a customer ID to manage manufacturing orders, holds, completion, and a measurement desk for site visits. Technicians and coordinators need order EJ3085 and request REQ-2026-002 in their pocket, with maps and an assignee, not a showroom carousel.
02
My role
I owned
- Work-app positioning (not a catalogue)
- Orders vs. Measurement information architecture
- Status filters, search, and request cards
- Flutter implementation and EN language switch
The team owned
- Manufacturing / ERP order pipeline
- Measurement scheduling rules
- Showroom photography and brand
03
The problem
Door manufacturing lives in two places that refuse to talk: the factory status of an order, and the villa where a technician must measure. If that coordination is a WhatsApp group, appointments slip and the line builds the wrong opening.
04
Discovery
Login is work: customer ID and primary phone, not email-as-identity. The bar is Home, Orders, Measurement, Profile. Orders filter by in progress / on hold / complete. Measurement is a desk: open, scheduled, info counts, then requests with maps, priority, timestamp, linked order, and assignee.
05
Product decisions
Identity is a customer ID
- The decision
- Sign-in with customer ID and phone-as-password, plus EN toggle — not a consumer social login.
- Why
- The users are accounts in the manufacturing system. Google login would be a lie.
- The trade-off
- Higher support for forgotten IDs. Higher alignment with ERP.
- The result
- The first screen says “manage your EuroDoor work.” The product never pretends to be a store.
Measurement is its own tab
- The decision
- Do not bury site visits inside order detail. Give them a desk with counts and filters (upcoming, needs approval, completed).
- Why
- A scheduled measure is a different job from watching manufacturing status.
- The trade-off
- Two lists to maintain. Clearer ownership in the field.
- The result
- A villa request can be approved, mapped, and assigned (e.g. sultan) without hunting through EJ3085.
Status as the primary filter
- The decision
- Chips for manufacturing states and measurement states, search by ID or address.
- Why
- Coordinators live in exceptions: on hold, needs approval — not in a chronological dump.
- The trade-off
- Less “inbox zero” romance. More ops realism.
- The result
- In progress vs. complete is a tap, not a report.
06
UX / user flow
Forest green, showroom photography, large sheets. Orders: search, chips, order card with manufacturing badge and recency. Measurement: glass summary counts, then request cards with Google Maps, Normal priority, datetime, order ref, assignee. Bottom nav is four work destinations, not five consumer toys.
07
Technical architecture
Flutter, ERP-backed orders and measurement requests, maps deep-links, bilingual hook (EN). Auth against customer accounts. Statuses are server enumerations so the factory and the phone cannot drift.
08
What I built
- Customer-ID sign-in and language toggle
- Orders list, search, and status chips
- Measurement desk with counts and request cards
- Maps, assignee, and order linkage on site visits
- Profile / home shell
09
Trade-offs
We did not ship a consumer configurator. Catalogue photography is atmosphere for a work tool. Install scheduling beyond measure, and customer self-serve tracking, waited. The field loop had to close first.
10
Launch
Internal/partner Flutter app for EuroDoor work on iOS and Android, aligned to manufacturing order IDs and measurement requests.
11
Outcome
Coordinators and technicians can see manufacturing state and site-measure state on a phone, with a map and an owner on each request. Factory throughput metrics stay with the manufacturer.
12
What I learned
B2B field apps fail when they look like e-commerce. The moment we said “manage your work” on the login sheet, the rest of the IA got easier. I would involve one technician in the measurement filters before naming them — upcoming vs. needs approval is a political distinction, not just a query.