Aviation utility · Mobile
ADU Aviation Mobile App
A one-week redesign concept focused on the core aircraft search, detail, sighting-log, and synchronization journey.
RoleProduct Designer
Duration1 week
PlatformMobile
StatusRedesign concept
Key decision
Focus the mobile journey on aircraft lookup and sighting capture.
The trade-off
Prioritizing the core task leaves broader desktop functions outside this redesign.
Current outcome
Mobile screens and a core task flow; outdoor use and synchronization recovery need testing.
Project summary
Move a desktop-linked aviation utility into a focused mobile workflow.
The available project material presents ADU as a companion for aircraft enthusiasts and existing desktop users. The design centers on quick lookup and logging in a mobile context, with records synchronized back to the desktop database.
Context to design for
- Information must be scannable on a small screen
- Primary actions need generous touch targets
- Aircraft identity and sighting details must remain distinct
- Synchronization state needs clear feedback
Evidence boundary
The files support the workflow and interface rationale, but not field-study findings, verified accessibility conformance, or measured speed improvements.
Core flow
Search → aircraft details → log sighting → synchronize.
1. Search
Find an aircraft with a prominent query field and scannable results.
2. Verify details
Review identity and aircraft data before recording a sighting.
3. Log sighting
Capture the essential observation details in a task-focused form.
4. Synchronize
Show whether the record is pending, synchronized, or needs another attempt.
Interface decisions
Prioritize action and legibility over dense utility screens.
Touch-first controls
Larger actions and spacing are intended to support one-handed use and reduce missed taps.
Strong content hierarchy
Aircraft identity, supporting details, and the logging action occupy distinct visual levels.
Visible sync feedback
A record should not appear safely stored until the interface confirms synchronization; pending and retry states remain proposed requirements.
Expected benefits
- Faster scanning and fewer competing actions
- Clearer path from lookup to recorded sighting
- More understandable synchronization feedback
Validation needed
Outdoor readability, touch-target suitability, sync recovery, and task speed should be tested with representative aviation users and real device conditions. These are design intentions, not verified results.
Next: AI-Powered Challenge Review
View case study