structure-app

Object-oriented UX (OOUX) structures apps around nouns—the core data entities users manage—rather than verbs or features. Extract objects, define their properties and states, map relationships, then derive screens and navigation from those objects. This maintains coherence as features grow and prevents information architecture from degrading.

Traditional navigation organizes around features or workflows (verbs); OOUX organizes around objects (nouns) and their relationships. Object-centered navigation reduces clutter in complex, data-rich apps by grouping related screens and actions per object, making the structure more scalable and intuitive as your app expands.

Identify core objects and supporting objects, define how they relate to each other, then derive primary and contextual navigation paths from those relationships. Each core object gets list, detail, and create/edit screens; contextual navigation connects related objects, preventing users from getting lost in complex data structures.

Use OOUX when your app manages multiple related data types, navigation feels cluttered, users frequently toggle between different 'things,' or your feature set keeps growing and degrading the IA. It's most effective for data-rich, complex applications where users interact with objects and their properties, not just linear workflows.

OOUX works for both new and existing apps. Start by extracting nouns from your current feature set, defining their properties and states, and mapping relationships. Then rationalize your existing screens around those objects and redesign navigation to reflect object relationships rather than feature silos.

Begin by identifying all nouns in your app—the 'things' users create, manage, and interact with. Extract core objects (primary entities users work with) and supporting objects (secondary entities tied to core ones), define their properties, states, and relationships. This foundation informs all subsequent screen and navigation design.