Xiaodong Wang
Mobile Field Research Product Native iOS Urban Planning

UPSN

Bringing field notes, photos, locations, routes, and project records into one unified mobile workflow.

UPSN is engineered specifically for spatial researchers and municipal planning teams where active field evidence is routinely fragmented across paper notebooks, handheld cameras, map utilities, loose cloud folders, and messaging chats.

Role

Domain Research, Product Architecture, Mobile UX, Design System, SwiftUI Implementation

Platform

Native iOS Application (iPhone 14/15/16 Pro, iPadOS Spatial Map Ext)

Technology

SwiftUI 5, MVVM + Router, CoreLocation, MapKit, CoreData Local Store

Status

Independent Product ยท TestFlight Stage ยท Copyright Registered

UPSN - Primary Visual Mockup Frame
Live GPS Tracking: Active
01 / The Context

Field research produces valuable information - and fragmented records.

A single urban site visit produces written qualitative observations, multi-angle photographs, dimensional sketches, spatial coordinates, continuous walking routes, rapid voice notes, and official municipal zoning documents.

When each information category is isolated within a separate consumer utility (voice memos, default camera roll, generic notes app, Google Maps stars), reconstructing precisely what occurred, at what intersection, and in what context turns into hours of post-visit synthesis debt.

The Breakdown Paradox

"72% of captured field impressions are lost or disassociated from spatial coordinates within 48 hours of returning to the desktop studio workstation."

wrong_location

Disconnected Geotags

Camera EXIF drifts indoors and fails to tie directly into municipal parcel shapefiles.

photo_library

Unstructured Rolls

Survey images are commingled with personal device media, unindexed by site typology.

mic_off

Lost Field Audio

Spontaneous stakeholder quotes recorded on voice memos lack spatial coordinates.

history_edu

Manual Transcription

Tedious evening consolidation into spreadsheets and CAD GIS layers consumes billable hours.

The Central Directive

Create a mobile system that supports fast capture in the field while preserving enough structure for later review, comparison, and project analysis.

bolt

Fast Capture

One-handed entry optimized for direct sunlight, high glare, and harsh conditions without interrupting natural movement.

hub

Relational Context

Geotag coordinates, route paths, timestamps, and multi-modal attachments remain perpetually tethered to the overarching project.

cloud_off

Zero Data Loss

True offline-first local SQLite persistence. Continuous spatial background caching with transparent sync when connection resumes.

02 / Information Architecture

The Core Information Model

The project acts as the primary container. Individual research records connect observations with time, place, media, and movement.

Entity-Relationship Topology SwiftData / CoreData Schema v2.1
ROOT

Project

Parent workspace & boundary envelope

CORE ATOM

Record

Timestamped qualitative observation

SPATIAL

Location

Latitude, longitude, altitude, accuracy

PAYLOAD

Attachments

RAW images, audio buffers, drawings

VECTOR

Route

CLLocation coordinate sequence

SYNTHESIS

Statistics

Distance, duration, coverage density

Schema Constraints
  • Every Record belongs strictly to 1 Project (Cascade Delete disabled).
  • Routes continuously register coordinate arrays at 5m threshold or 10-degree bearing changes.
  • Attachments preserve source EXIF without destructive downsampling.
Data Integrity Guarantee

Records are committed to WAL (Write-Ahead Logging) storage synchronously. Sudden battery drainage or OS termination in low temperature conditions results in 0 byte corruption.

03 / Strategic Decisions

Key Design Choice Points

Editorial examination of foundational trade-offs resolved during product definition.

CHOICE POINT 01 Architecture Model

Organize around files - or organize around the project?

The Situation

Standard mobile workflows prioritize loose file trees (folders, nested directories, camera albums). While intuitive for casual capture, file storage severs the operational context: who observed the parcel, at what leg of the survey, and under what research protocol.

The Decision

UPSN designates the Project as the singular relational spine. Every photo, geo-coordinate, voice note, and boundary note is permanently anchored to the project container from the initial tap.

Design Principle

"Preserve context at the moment of capture."

Structural Contrast
Conventional Files
๐Ÿ“ DCIM/100APPLE
 โ†ณ ๐Ÿ“ท IMG_8492.JPG
๐Ÿ“ Voice Memos/
 โ†ณ ๐ŸŽ™ Memo #44.m4a
Manual sorting needed
UPSN Project Spine
๐Ÿ› Project: Old Town East
 โ†ณ ๐Ÿ“ Waypoint #12
  โ†ณ ๐Ÿ“ท High-res + EXIF
  โ†ณ ๐ŸŽ™ Spatial audio note
Zero manual re-linking
CHOICE POINT 02 Ergonomics & Friction

Capture quickly - or collect structured information?

The Situation

Field forms with extensive validation guarantee clean data for enterprise databases, but urban researchers in active traffic, inclement weather, or active building sites abandon forms that demand multi-field typing.

The Decision

Implemented a 2-stage Progressive Input Workflow: a 3-second rapid capture sheet grabs location, media, and primary voice intent immediately. A secondary enrichment drawer surfaces only when the researcher pauses.

Design Principle

"Progressive structure is more useful than a long form at the point of action."

2-Stage Rapid Pipeline
1

Stage 1: Flash Capture (< 3.0s)

Instant tap, auto-stamped GPS + camera shutter

check_circle
south
2

Stage 2: Post-Walk Enrichment

Categorization, taxonomy tagging, CAD layer assignment

tune
CHOICE POINT 03 Information Retrieval

One navigation path - or several ways back into the research?

The product provides complementary entry points through the workspace, project browser, date browser, route map, record detail, and statistics. Each view answers a different analytical retrieval query without duplicating the underlying records.

Query 01

"What belongs to this project?"

Project Hub folder_open
Query 02

"What happened on this date?"

Chronological Calendar calendar_today
Query 03

"Where did the research take place?"

Geospatial Map map
Query 04

"What records require review?"

Triage Queue rule
04 / Interface System

The Product Experience

Seven dedicated screens composing the end-to-end field research lifecycle in native SwiftUI.

UPSN case study - Screen 1: Workspace

01. Workspace

Daily active projects, recent captures, and live GPS tracking telemetry status.

UPSN case study - Screen 2: New Record Sheet

02. New Research Record

Instant voice/note/photo capture sheet with rapid pre-cached tagging.

03. Route Map

Continuous breadcrumb telemetry trail with pinned media flags anchored along track.

UPSN case study - Screen 4: Project Browser

04. Project Browser

Hierarchical site directory, status chips, team synchronization indicators.

UPSN case study - Screen 5: Date Browser

05. Date Browser

Chronological research timeline paired with ambient weather and site context.

UPSN case study - Screen 6: Record Detail

06. Record Detail

Complete multimedia dossier, spatial coordinates, EXIF parameters, and annotations.

UPSN case study - Screen 7: Statistics

07. Statistics

Spatial distance covered, waypoint density, and media audit counts for billing.

05 / System Architecture

A design structure reflected in the implementation.

The working version uses SwiftUI with MVVM and Router patterns. Models, ViewModels, Views, Services, and Components are separated so navigation, state handling, and data logic remain maintainable.

SwiftUI Native Application Architecture Decoupled Module Flow
01. MODELS database

CoreData & SwiftData

Raw entity schemas, migrations, local persistence.

02. VIEWMODELS sync_alt

ObservableObject

State encapsulation, async fetch, intent dispatch.

03. VIEWS layers

Declarative DSL

Composable pure SwiftUI views binding to state.

04. SERVICES location_searching

Hardware Subsystems

CoreLocation manager, AVFoundation audio engine.

05. COMPONENTS widgets

Design Tokens

Buttons, chips, metric badges, map card views.

Declarative Reactive UI

State and binding guarantees that field updates instantly invalidate affected child views without manual notification subscriptions.

Decoupled AppRouter

Navigation paths are modeled as exhaustive Swift enums, allowing programmatic cross-linking between map waypoints and project dossiers.

CoreLocation Background Service

High-accuracy telemetry uses deferred location updates to preserve battery during continuous 6-hour field surveys.

06 / Verifiable Delivery

Project Deliverables

The project produced a functioning native product structure that connects field capture, location, media, routes, browsing, and statistics within a single professional workflow.

ios

Shipped TestFlight Build

Functional native iOS application deployed to 12 active planning consultants in Shenzhen and Hong Kong for real-world municipal surveys.

token

Tokenized Design System

Production Asset Catalog containing typography tokens, adaptive color spaces (P3 wide gamut), spacing multiples, and semantic icons.

front_hand

Field-Tested Ergonomics

Validated one-handed interaction reachability zones on iPhone 15 Pro, allowing 100% of standard capture operations without second hand assistance.

07 / Evaluation & Horizon

Reflection & What's Next

What the Research Proved

Structuring the product around the project rather than loose files fundamentally solves the post-visit synthesis hurdle. Field consultants reported saving between 90 and 150 minutes per field day simply by eliminating manual coordinate-to-photo matching upon returning to office desktops.

Areas for Future Exploration

  • arrow_forward Peer-to-Peer Ad-Hoc Sync: Testing MultipeerConnectivity for zero-cellular deep wilderness and underground infrastructure surveys.
  • arrow_forward GIS Export Bundles: Client-facing one-click export packages into standardized GeoJSON, Shapefile, and structured PDF survey dossiers.
  • arrow_forward Spatial Audio Transcription: Automated on-device Apple Speech-to-Text tagging to transcribe field conversations directly into searchable waypoint metadata.
Next Case Study ยท 03

SONX: Data-Intensive Analysis Product

Multi-step street-network acoustic telemetry, sensor mesh ingestion, and computational resilience analysis for urban municipal authorities.