Most decision-making apps are stuck in 2012—they're overflowing with ads, complicated menus, and corporate sterility. Ironically, they add even more “friction” for users who are already suffering from decision fatigue.

It was necessary to understand how users resolve dilemmas and how to shorten the path to a solution without losing anything necessary and discarding anything unnecessary.

The user journey helps to understand how users behave, while the wireframe helps to quickly understand which elements and what information are needed. All of this is information architecture, which allows to make application simple and understandable.

Fast prototypes & quick tests. At this stage, I was able to test the prototypes and draw the main conclusion: most actions should be at the bottom or start from the bottom. This is for the convenience of using the app with one hand.

The colors chosen for dilemmas play a very important role in the UI. The color palette was selected so that the cards would match each other and comply with accessibility standards. The interface remains unchanged on all backgrounds, ensuring accessibility and visual pleasure in any state of the application.

I moved away from standard flat lists and created a modern multi-level interface. Treating each dilemma as a physical object, I established a clear hierarchy that organizes dense information using the depth of the Z-axis. This is not just an aesthetic choice, but a strategy for maintaining contextual continuity during complex transitions.

Implementing these transitions with common elements required a connection between design and engineering. Acting as a systems architect, I ensured that the morphing effect was natural and smooth, creating a high-quality experience that static screens simply cannot convey.

Instant saving: uses an interface similar to Notion, where every keystroke is automatically saved. No “Save” buttons, no lost data, no frustrations.

Smart naming: Context is assigned automatically (e.g., “Dilemma #8”), allowing users to move to the decision stage faster.

Limited design: the Solve trigger will not appear until there are at least two solutions and the hint is saved.

Result: for the final decision, there will be a Casino spinner animation, which is designed to evoke additional emotions when making a decision.

The illustrations were created in the same style and color scheme. It is important that they match the colors of the cards.

Instead of writing code in the traditional way, I acted as an AI Orchestration, using Google Antigravity (Cursor-based AI) to implement complex logic. This allowed me to focus on high-level architecture and UX patterns, delegating the syntax of the neural network.

Platform Strategy: A unified code base on React Native for iOS and Android.

State Persistence: Instant auto-saving implemented via Zustand. Every data entry is recorded without the need for “Save” buttons.

Fluid Interactions: Achieved a stable 60 FPS for “Modern Stack” animations and seamless Shared Element Transitions.

I openly shared every stage of Dilemm's creation on my LinkedIn.
Below is a chronology of the product's development from the first idea to a working build:
First post
Part 2. Problem Engineering
Part 3. Wireframes
Part 4. Usability test
Part 5. User interface
Part 5.1 User interface
Part 6. Start of development
Part 6.1 Continued development
to be continued...