hig-ooui-mobile-design

To design mobile apps with OOUI modeling under HIG constraints, define primary objects, attributes, and actions, then translate them into task flows, navigation structures, and wireframes that conform to platform HIG checklists.

OOUI modeling for mobile design maps conceptual objects, attributes, and states into a coherent UI vocabulary. You need it when translating conceptual models into concrete UI deliverables like wireframes and component guidance.

To translate an object model into task flows for iOS, convert defined objects into primary and secondary task flows, then organize entry points and navigation patterns per platform HIG guidelines to produce screen plans.

Yes, you can generate Android design deltas and SwiftUI component notes from an OOUI model. The design process produces cross-platform guidance including platform-specific deltas and component notes when requested.

To create Figma wireframe instructions from a conceptual object model, define primary objects and their relationships, derive task flows, and output wireframe instructions aligned with OOUI templates and visual aesthetics guidelines.

Yes, this approach supports watchOS and iPadOS navigation design. It applies OOUI modeling across iOS, iPadOS, and watchOS projects to organize entry points and navigation patterns per platform HIG guidelines.