Anonymous relationship advice app where every question gets two answers from a married couple, one from a man and one from a woman, side by side. A focused iOS MVP shipped on FlutterFlow with the paid tier built in from the start.

People rarely get balanced relationship advice. They ask one friend, or one app, and get one point of view. Both Sides set out to fix that. The idea was simple: let anyone ask a relationship question anonymously and get an answer from a married couple, one reply from a man and one from a woman, side by side.
The audience is anyone wrestling with something they would rather not say out loud, on subjects like trust, conflict, intimacy, and parenting. The brief was a focused mobile MVP for iOS, shipped on FlutterFlow.
Advice is only as good as the perspective behind it, and most advice comes from a single voice. That is a problem for questions where two people see the same situation completely differently. The subject matter is also sensitive, so the product only works if people feel safe using it.
The brief had three hard constraints. Ship the core ask and answer loop quickly, protect anonymity at every step, and build the paid tier in from the start rather than bolting it on later.
Aumadi handled the full build, from the app to the backend, minus a separate admin portal that was kept out of the first release to stay lean.
We chose FlutterFlow so a single codebase could carry the product to launch fast, with Supabase behind it for data and auth. Firebase covered push notifications and Resend handled email. Where the no-code layer ran out of room, custom Node and Flutter functions filled the gap.
The UX philosophy was trust first. Asking a question had to feel completely safe, so signup is nothing more than a nickname. Reading answers had to make the two viewpoints easy to compare, so the male and female responses live in a clean split card. Monetization was designed in, not bolted on: a free standard answer, with one-time priority and a monthly membership that adds faster replies and follow-up chat.
Discovery and planning. We split the work into a tight MVP and a phase 2. The MVP carried the question to answer loop, anonymous accounts, categories, and payments. A full advisor onboarding flow was parked for later so the first release could stay focused.
Design. The design centered on two screens: the ask flow and the dual answer view. Both were kept calm and uncluttered, because the subject matter is sensitive and the product only works if people feel safe using it.
Development. FlutterFlow drove the front end, Supabase the backend. We built anonymous signup, category-based questions, the split male and female answer display, push notifications, and the full payment layer across one-time and subscription billing. Custom functions handled the logic the visual builder could not.
Testing. We tested the flows that matter most: signing up, asking, paying, and receiving a pair of answers. The focus was reliability and privacy, making sure nothing revealed who the user was.
Launch. The app shipped to the App Store with the full MVP feature set. The build was kept clean so the founding advisors and the first users could step straight in.
The outcome. Both Sides is live on the App Store. Phase 2 is already in planning, starting with advisor onboarding to grow past the founding couple into a wider panel.
Most advice gives you one voice. Both Sides gives you two, and that is the whole point.



30-minute discovery call. Scope, timeline, and fixed quote out the other side. No strings attached.