← AstroMatrix Reports — all pages
The Matrix Question
Product brief · AstroMatrix · September 2026
The screen that already works, and why people still leave
The Matrix is the most-reached screen in the app after Home, and the second best at bringing people back. It is also the same screen every single time you open it. This is about closing that gap.
Written for product · evidence from the Sept 11 production scan, in-app support and store reviews
The position
The Matrix is our simplification, not our complexity
It takes a birth chart — 29 bodies, several hundred aspects, a vocabulary that takes years to learn — and turns it into five words anyone can read: Purpose, Harmony, Love, Abundance, Evolution.
That is the whole product thesis in one screen. Someone who knows nothing about astrology can open it and understand what they are looking at. No competitor ships the depth underneath it, and almost none ship a way in that is this gentle.
The numbers say it works.
68.8%of tracked accounts reach it — more than any screen except Home
29.1%never come back — second lowest in the app, behind only interpretations
1 of 49UI complaints that actually name the Matrix as too complex
That last figure is the one to sit with. We have spent months treating "the app is too complex" as a Matrix problem. Of roughly forty-nine people who complained about the new interface, exactly one said the Matrix itself did not make sense. Everyone else said a version of "I cannot find a thing I already know exists."
Those are opposite problems with opposite fixes. Simplifying a screen that is already the simplification would make the product worse.
And because the Matrix's parts also render inside Home, the Moon screen and the weekly report, anything we improve here lands on six surfaces at once. It is the highest-leverage screen we own.
Three journeys
Where people actually fall out
Journey oneThe newcomer, thirty seconds after signing up
They finish a four-step setup — name, what they care about, birth date, birth place — and are dropped straight onto the Matrix, on the category they chose. This screen is the payoff for signing up.
What they get is a radar chart and a grid of scored categories. After four screens of questions, the reward for answering is one more thing to navigate.
The break: we asked them what they cared about and then handed them a menu instead of an answer. Reading one interpretation is the sharpest activation threshold we have measured — activity jumps from 2.7% to 17.9% once someone reads one. We route them to the door and do not walk them through it.
Journey twoThe returner, on their fourth visit
They tap the Matrix tab. They see what they saw last time. Same categories, same scores, same cards, in the same order.
By default the screen shows everything it knows at once — their birth chart and every current transit, merged into one list. Nothing says what is permanent and what is passing. Nothing says what is happening today.
The break: a screen that never changes gives no reason to come back tomorrow. Our retention is a smooth slide, not a cliff — 94% reach a second visit, 78% reach a fifth, 41% reach a twentieth. That shape is what "no fresh reason to return" looks like.
Journey threeThe person who was sent a link
A friend shares their compatibility. The link opens the Relationship Matrix. Roughly half of these people are gone inside ten seconds — and among people arriving cold from a share link, 93% leave in under ten seconds. It is the worst-performing surface in the app.
What greets them: no time filter at all, so there is nothing about right now. And in the default view, no Report button — the screen's main action is simply not rendered until you change a setting you do not know exists.
The break: this is also our best monetisation signal. Adding a second chart moves conversion from 20.7% to 51.2%. The relationship surface is where that happens, and it is the one we have finished least. 72% of accounts have never opened it.
What people say
Almost every complaint is the same complaint
 Can no longer see yearly things like time lord and profection year.Google Play review
Time lord and profection year are on the Summary tab. They were never removed. This is the fourth separate confirmed case of a live feature being reported as deleted — the others were weekly and monthly transits, solar return interpretations, and saved charts.
 Everything looks the same, no visual differentiation to find what I need.In-app support
This is the actual problem, said plainly. Not too much, not too hard — too flat. When every card looks like every other card, the eye has nowhere to land, and a person who knows the feature exists still cannot find it.
 The new matrix system doesn't make sense, difficult to read through.In-app support — the one complexity complaint in forty-nine
Worth taking seriously as a minority signal, not as a mandate. "Difficult to read through" is closer to the flatness complaint above than to a request for fewer features.
The pattern across all of it: we are not failing to give people enough. We are failing to tell them what they are looking at.
The bets
Five moves, in the order I would make them
1
Make the screen different every day
Right now cards are ordered by category — houses, then aspects — which never changes. But every card already knows whether its influence is active right now and how close it is to peaking. We compute this for every item and then ignore it completely.
Sort by what is live and cresting today. Badge the active ones. The screen then changes on its own, every day, because those values move on their own.
Highest returnSmall buildNo new dataNo design decision needed
Why this one first: it is the only fix on this list that gives people a reason to return tomorrow, and it needs nothing we do not already have. It also sidesteps the argument about which default view is correct — the screen becomes time-aware without anyone choosing a default.
2
Answer the question instead of showing the data
Every category already carries a pair of words and a count — Passion against Distance, Success against Obstacles, eight supporting influences against two challenging ones. The screen holds all of it and displays only the category name.
Put one line under each category: "Intimacy & Romance — Passion 8, Distance 2." That is the difference between a chart and an answer, and it is the thing the setup flow implicitly promised.
It also fixes a quieter problem: the score bars scale to each person's own maximum, so no number on the screen means anything in absolute terms. Words give it a direction even when the bar does not.
High returnSmall buildFree — no AI costTranslates like everything else
Keep the AI where it is. The deep written report stays behind the button — that is the payoff for tapping in, and it is genuinely good: people who reach a report spend 1.4 minutes there and 90% do not bounce. This line is the free thing that sits above it and makes the number mean something before you tap.
3
Fix the relationship first-run
Our worst-performing surface is also our strongest conversion signal. Three things are wrong on arrival:
The main action is invisible. In the default view the Report button is not shown at all. There is a real engineering reason behind it, but the user just sees a screen with nothing to do.
There is no "right now". The solo Matrix has weekly, monthly and all-transits views. The relationship side has none — it can only ever show the permanent picture. Three missing options, against an engine that already supports them.
We pick their partner for them. If an account has exactly two people saved, opening the Relationship Matrix silently pairs them and remembers it — changing what every other relationship screen shows, without asking.
Highest commercial upsideMedium buildOne engineering unknown
The unknown: the hidden Report button was disabled because that specific report was thought to be too large to save. The reasoning does not match how the app actually saves it, and the real limit looks to be roughly fifty times larger than the report. One measurement settles whether it can simply be turned back on.
4
Stop features from feeling deleted
Four confirmed cases of people reporting removals that never happened. The Matrix makes this worse in a specific way: influences that have finished quietly disappear from the list. Correct behaviour, never explained. Someone who saw an aspect last week and cannot find it today concludes we took it away.
Two cheap moves: say when a view is empty and why, instead of showing a blank panel; and give finished influences a visible "ended" state rather than vanishing them.
Medium returnSmall buildReduces support load
The wider version of this problem is that our depth is invisible: synastry is seen by 1.5% of accounts, composite by 0.3%, the store by 0.2%. We are not short of things to sell. We are short of people finding them.
5
Don't lose people's reports
When a report is generated but fails to save — a network blip — we show a warning with a "View Now" button so the person can still read what they waited for. That button goes nowhere. It has never worked.
Rare, but it lands at the worst possible moment: right after we told someone their thing was ready, and then lost it.
Low volumeTiny buildHigh indignation per occurrence
Restraint
Three things I would not do
Don't rename the Home buttons
The standing recommendation is that people cannot find weekly and monthly transits because the buttons do not say "transits". But the two people who reported it asked "where is the weekly and monthly forecasts" — and the buttons say exactly Weekly and Monthly. They used our words and still did not find it. The label is not the barrier; where it sits on the page probably is. Check that on a phone before spending anything on naming.
Don't change the default view on instinct
It is tempting to switch the opening view from everything-at-once to transits. But we have no A/B framework, no way to tell one session from another, and no app-version tag on our stats — so we would be swapping a default we cannot grade, and we would not know for months whether it helped. Bet 1 makes the screen time-aware without needing this decision at all. Make it later, with evidence.
Don't simplify further
One person in forty-nine called the Matrix too complex. The rest could not find things. Removing depth would answer the minority and damage the majority — and the depth is the only thing competitors cannot copy quickly.
The blocker
We cannot currently tell whether any of this worked
Everything we measure is screen-level: how many people reached a screen, how long they stayed, whether they came back. Nothing tells us what they were trying to do or what they tried just before giving up.
Concretely, we are missing three things, and each one blocks grading the bets above:
Session-level events — we count screen views, not app opens, so "visits" means something different from what everyone assumes when they read it.
An app-version tag on stats — without it, no change we ship can be separated from any other change we ship. This is also why we still cannot settle whether last quarter's tourist-rate spike was a real regression or a measurement artefact.
Any A/B capability at all.
None of this should stop bets 1, 2 and 5 — they are small, obviously directionally right, and cheap to reverse. It should stop us from making expensive or irreversible calls, like the default view, until we can read the result.
There is one free measurement available today: we can already tell whether a person has ever changed the Matrix's view filter, because choosing one leaves a trace and never choosing one does not. Nobody has ever counted it. If that number turns out to be 3%, the whole default-view debate is settled by the data rather than by argument.
Evidence: production scan of 11 Sept 2026 covering 102,600 tracked accounts — the first pull after the instrumentation fix released on both platforms, so the first trustworthy one. Complaint analysis from 45 days of in-app support (756 users) plus store and Facebook backlogs. Conversion and activation thresholds from the user-modes work. The engineering detail behind bets 3 and 5 is filed separately as issues 131, 132, 136 and 137.