Aztruz App
Designing an Astrology-Based Dating App from Zero · Android & iOS Jul 2026 – Aug 2026

My Rol
UX Lead
IxD
UIKit - Design System
I owned UX and UI from the first client conversation to the QA of the built app. The project had no UX budget, so I started from the user stories and defined the architecture, flows, interaction patterns and interface myself. The client gave me the freedom to fix the problems I found.
What Makes This Project Different
This was a new product with no legacy to redesign. The challenge was combining two domains that rarely work well together: astrology content (natal chart, numerology, synastry) and a dating mechanic (matching, chat, safety), in one coherent mobile product with no planned UX role.
The Problem
The client wanted an app where astrological data drives matching: natal chart, daily horoscope, synastry and an AI "Oráculo" that suggests matches. The initial scope was a list of user stories, with no architecture, flows or interaction criteria. The risk was a feature-heavy app that asked for too much data at signup, hid its monetization logic and left safety (reporting, blocking, photo moderation) undefined. The goal: turn those stories into a usable product that monetizes without breaking trust.
Process — From User Stories to a Tested Prototype
Mental map
Hierarchy Map
User flow


Validation with stakeholders

Full prototype
Interface Design — Decisions Built for Trust and Retention






Beyond the Brief
The user stories covered business logic but left design gaps that I solved on my own initiative: the ad flow (cooldown, rewarded video, no-fill fallback), user reporting with mandatory evidence, empty and limit states, explaining what is lost without birth time, selfie verification, and accessibility. The business rules (70/30 matching, photo reveal, moderation) came from the client; my contribution was turning them into clear, trustworthy experiences.
UX-QA
During development I took the UX-QA role: reviewing the Flutter build against approved designs, Material 3 consistency, interaction patterns and states, and logging every deviation. Having done the design, I could tell quickly when something drifted.
From Zero to a Complete Product
Starting Point
A list of user stories
No architecture or flows
No error, empty or safety states
No UX budget
Result
Professional IA and documented flows
Complete prototype tested on device
Consistent Material 3 patterns
Safety, monetization and edge cases designed
A client very happy with the outcome