Local case-study draft · Client asset and publication approval pending
LinkedIn
Connected productIoT · Commerce · Operations

MEISPACE

Smart-home control, shopping and operations in one connected product system.

Sagiam designed and developed the represented MeiSpace apps, commerce experiences, connected services and operational tools.

Customer apps
BUILT
Device operations
BUILT
Commerce
BUILT
Setup concepts
DESIGNED

Production status and measurable outcomes are pending client confirmation.

BUILT UI · SYNTHETIC DATAMeiSpace device fleet administration interface with synthetic empty data
BUILTMeiSpace switchboard control screen for six switch circuits and a fan
BUILTMeiSpace customer app device list
Bluetooth setupSix switches + fanOffline stateCommerceOperations

One connected product ecosystem

One product had to connect a physical panel, customer apps, shopping and daily operations.

Each surface has a different job, but customers and operators need the same clear device, order and support states.

Built

Smart-home app

A customer experience for setting up a home, adding a panel and controlling configured circuits.

  • Homes and rooms
  • Nearby setup
  • Switch and fan control
  • Sharing, usage and support
Built

Commerce app and web

Product discovery and ordering journeys connected to customer accounts and fulfilment records.

  • Browse products
  • Cart and checkout
  • Orders and fulfilment
  • Account and after-sales
Built

Connected service layer

Application services coordinate device requests, product workflows and operational records.

  • Authenticated requests
  • Device lifecycle
  • Command and state handling
  • Operational records
Built

Operations console

Tools for finding a problem, understanding the current state and recording the next action.

  • Device fleet
  • Provisioning and alerts
  • Connection health
  • Repair, warranty and audit

Guided device setup

A hardware task becomes a clear, guided journey.

The app explains what it needs, where setup has reached and which step needs attention.

Prepare

Turn on Bluetooth and Wi-Fi.

Find

Discover the nearby panel.

Connect

Share the selected network locally.

Confirm

Check network and service readiness.

Add

Place it in a home and room.

Recover

Explain the failed step and retry.

Prepare the phoneDESIGNED · Setup preflight concept
Find the panelDESIGNED · Nearby discovery concept
Connect the networkDESIGNED · Synthetic network details
Recover clearlyDESIGNED · Stage-specific help
Built MeiSpace control screen showing switch and fan controls
Built MeiSpace customer device list

Command and confirmation

A tap begins a command lifecycle. It does not blindly assume the device changed.

The documented TCH7-6S1F panel represents six switch circuits and one fan circuit. The customer interface can show waiting, confirmed and offline states based on what the system knows.

  • Six switch circuits
  • One fan circuit
  • Bluetooth used during nearby setup
  • Wi-Fi and device messaging after setup
  • Offline presence represented
  • Reconnect state restored
Illustrative workflow

The request has been sent. The app waits for a device acknowledgement or state report.

Customer requestCommand recordedDevice messageAcknowledgement or reportApp updated

When the connection changes

The product stops claiming certainty and gives people a path forward.

The workflow was built to make common setup, control and support problems visible and recoverable.

01

The connection is lost

The connected service receives an offline presence state when the panel loses its network path.

02

The app shows what is known

The customer can see unavailable or last-known state instead of an unsupported confirmation.

03

The device reconnects

A bulk state report can restore the known switch and fan state after the connection returns.

Setup retryCommand timeoutWi-Fi changeDevice reassignmentRepair requestWarranty support
Internal commerce concept showing product discovery
Designed · Internal concept · Synthetic content
Internal commerce concept showing a shopping cart
Designed · Internal concept · Synthetic content

Commerce connected to fulfilment

One checkout can still give the team control over each fulfilment.

Self and downline cart lines enter one checkout and payment context. Operational child orders can then carry their own shipment, status, cancellation or refund path.

  • Product discovery
  • Cart and checkout
  • Self and downline ordering
  • Parent payment context
  • Child-level fulfilment
  • Order history and support
One checkout and parent payment
Item A
own fulfilment state
Item B
own fulfilment state
Item C
own fulfilment state

Reporting-led marketing operations

Activity becomes a clearer basis for reviewed action.

MeiSpace connects commerce, referral, fulfilment and device activity to operator-facing reporting, giving teams a clearer basis for reviewed customer, campaign and service decisions.

01Customer and order activityStructured records provide the starting point.
02Filtered reportingTeams find a segment, problem or opportunity.
03Team reviewA person checks the context before acting.
04Approved follow-upAn offer, message or service action is prepared.
05Result checkedReporting shows what happened next.

Rules-based and reviewed by people

Operations and recovery

The back office is organized around investigation and control.

These built interfaces are shown with synthetic empty data. No production customer or device records are displayed.

Device fleet · BUILT UI · SYNTHETIC DATA
Energy views · BUILT UI · SYNTHETIC DATA
Repair · BUILT UI · SYNTHETIC DATA
Warranty · BUILT UI · SYNTHETIC DATA
Audit history · BUILT UI · SYNTHETIC DATA
Security settings · BUILT UI · SYNTHETIC DATA
Operational dashboardDevice fleetProvisioning funnelDevice messaging healthEnergy viewsRepairWarrantyFirmware / FOTAAudit historySecurity settings
01Find the device, customer or incident
02See current and last-known state
03Take an authorized action
04Keep the action in history

Engineering foundation

Technology selected around the product journey.

The reviewed implementation spans customer applications, commerce, device messaging and operational tools.

FLCustomer appsFlutter applications
NXCommerce and adminNext.js and React
JSApplication servicesNode.js and Express
DBOperational recordsMongoDB and Mongoose
BTNearby setupBluetooth Low Energy
MQDevice messagingMQTT-backed flow
Device lifecycle

Homes, rooms, device claim, command state and reconnect handling.

Commerce operations

Checkout, parent payment and child-level fulfilment records.

Operational control

Roles, permission interfaces, support paths and audit history.

Evidence and status

Clear about what was reviewed and what remains pending.

BUILT

An implemented repository surface or workflow reviewed in the supplied project evidence.

DESIGNED

A reviewed design concept that is presented as a concept rather than a released screen.

SYNTHETIC DATA

An interface captured without production customer, order or device records.

PENDING

Publication, production availability or measurable outcomes still require confirmation.

The evidence demonstrates implemented software and product workflows. Production availability, public integrations and measured business results require client confirmation.

Build the complete product experience

Building a product that connects hardware, customers and operations?

Show us the device, the users and the business process. We will help you plan the app, connected services and operational tools around how the product must work.

Device onboardingCustomer applicationsConnected controlEcommerceOperations dashboards