Home/Books Lobby/Modern Solution Design™/Chapter 16
Part V · Mobile & Multi-Channel
Chapter 16 of 24

Mobile-First & Multi-Channel Strategy™

Deciding What Belongs Where — Module by Module, Not App by App

Mobile is not a smaller version of the desktop.

It is a different job, done by a different tool.

Chapter Objective

Give teams a repeatable framework for deciding what belongs on web, mobile, tablet, or another channel entirely — module by module, not as a blanket "let's build an app" decision.

  • Mobile By Purpose™
  • Role-Based Mapping
  • Offline-First Design
  • Responsive vs. Adaptive
  • Field Capture Tools
  • Multi-Device Continuity
01Section 01

Mobile By Purpose™

Don't ask "should this be on mobile?" Ask "what does this task actually need?"

Desktop

  • Planning
  • Reports
  • Analysis
  • Configuration

Mobile

  • Approval
  • Photo & Signature
  • GPS & Barcode/QR
  • Voice
02Section 02

Construction ERP Case Study™

The clearest real-world illustration of the whole chapter's principle.

FunctionWeb (Back Office)Mobile (Site)
Planning & Budget
Master Data
Procurement & Payroll
Site Photos & Inspection
Material Requests
Attendance
Approvals
Safety Checks
03Section 03

Channel Decision Framework™

Five questions decide the channel — before any screen is designed.

  • Does the task need a large screen for planning or analysis?
  • Does it require reading or entering a lot of structured data?
  • Is the person physically moving while doing it?
  • Does it need camera, GPS, or a device sensor?
  • Is speed of completing one single task the priority?
04Section 04

Role-Based Channel Mapping™

The same ERP, mapped differently for every role.

Site Engineer
Mobile
Project Manager
Web + Mobile
Finance Controller
Web
CEO
Web + Mobile Dashboard
05Section 05

Responsive vs. Adaptive™

Resizing is not the same as redesigning for the channel.

Responsive

Same layout, resizes — good for reports and dashboards.

Adaptive

Different UI per device — Approval Screen is a table on web, a swipeable card stack on mobile.

06Section 06

Offline-First Mobile™

A field app that stops working without signal isn't a field app.

No SignalLocal StorageQueue ActionsReconnectAuto Sync Conflict Resolution
07Section 07

Field Capture Tools™

The sensors a phone has, that a desktop never will.

Camera
GPS
Barcode / QR
Signature Pad
Voice Notes
NFC
Biometric
08Section 08

Progressive Web vs. Native™

A real trade-off, not a default — chosen per project.

CapabilityProgressive WebNative
InstallationNo app store
Offline SupportPartial
Push NotificationsLimited
Camera / GPS Access
Update Speed InstantStore review
09Section 09

Multi-Device Continuity™

Start on one device, finish on another — same record, same state, no re-entry.

Start on MobileContinue on Tablet Finish on Desktop
10Section 10

Tablet as the Middle Ground™

Between the phone's speed and the desktop's depth.

Site Supervisor Dashboard
Inspection Checklist
Signature Collection
Digital Forms
11Section 11

Cross-Channel Notifications™

The same event, delivered consistently wherever the user actually is.

Push
Email
SMS
WhatsApp
12Section 12

Industry Web/Mobile Matrices™

Construction isn't unique — every industry has its own split.

Healthcare

FunctionWebMobile
Scheduling & Billing
Bedside Charting
Medication Scanning

Field Sales

FunctionWebMobile
Pipeline Analytics
Customer Visit Check-in
On-Site Order Capture

Facility Management

FunctionWebMobile
SLA & Contract Config
Fault Reporting
Technician Dispatch
13Section 13

Bandwidth-Aware Design™

A field site is not an office network — design for it explicitly.

Low BandwidthCompressed ImagesText-First Sync Later
14Section 14

Wearables & Emerging Channels™

The channel list keeps growing — design the strategy to extend, not restart.

Smart Watch
AR Glasses
Voice Assistant
Vehicle Display
Kiosk
15Section 15

Channel-Specific Security™

A lost phone and a stolen session are different risks — plan for each.

Mobile

  • Biometric Login
  • Remote Wipe
  • Device Management

Web

  • Multi-Factor Auth
  • Session Timeout
  • IP Restriction
16Section 16

Testing Across Channels™

A field app tested only in an office never survives the field.

  • Test on real devices, not just emulators
  • Test offline and low-signal scenarios
  • Test with gloves and in direct sunlight
  • Test on slow and unstable networks
  • Test across different screen sizes
17Section 17

Future Multi-Channel Enterprise™

The channel finds the person, not the other way around.

Ambient Computing
Voice-First ERP
AR Field Overlays
Predictive Channel Switching

Multi-Channel Strategy™

One channel strategy, ten destinations — chosen module by module.

Channel Strategy
Web
Mobile
Tablet
Wearables
Voice
Kiosk
AR / VR
Email
SMS
WhatsApp

Multi-Channel Intelligence™ (MCI™)

Every module in an enterprise application should pass through these ten checkpoints before a channel is chosen.

MCI LayerDesign Question
Task NatureIs this task analytical or physical?
LocationWhere is the user when they perform it?
SensorsDoes it require camera, GPS, or biometrics?
ConnectivityCan it tolerate an offline environment?
Data VolumeHow much information must be entered or reviewed?
SpeedIs completing the task in seconds critical?
ContinuityMust the task move across devices mid-way?
SecurityWhat risk does this channel introduce?
RoleWhich persona performs this task most often?
Future ChannelsCould this task extend to voice, wearables, or AR later?

The right channel isn't the one that's easiest to build.
It's the one the task actually needs.

Chapter 17 goes deeper into the field itself — Field Productivity by Design, where offline sync, GPS and biometric attendance become concrete, buildable patterns.