account

Summary

Everything about you: how you are paid, what currency, what the app looks like, and how to leave.

Raw wireframe

• .context/designs/mobile/settings/account.html

Why it is drawn this way

Pushed off the header avatar on balances, not given a tab. It is visited twice a year, and the slot it held went to spending, which people open every week. A tab is for a place you return to; a push is for a place you go, do a thing and leave.

Payment details, currency and appearance were each a whole ROUTE reached only from here, holding one control apiece. Three taps and three transitions to change a setting you were already looking at. A row whose subtitle has to summarise the screen it hides is the shape of the problem — delete the screen. Scrolling beats navigating.

A bank method can no longer be ADDED, and existing ones stay. Aakalan cannot initiate a transfer, so a full account number and IFSC would be credentials collected for no purpose — and last-four-only left the row unable to do the one thing a payment method exists for. Nobody can pay it; it was a note to yourself wearing the costume of a payee. Narrowing the type would have silently deleted somebody's own record of where they sent the rent.

Export is never Pro and covers the whole ledger. See pro-never-gates-the-core-loop.

"What Aakalan does not do" is PRINTED, not a link. It was a "Privacy & data" link out to a web page, which is the thing the design argues against in as many words: a privacy page nobody opens is a privacy page that says nothing. Three claims, on the screen, readable without leaving the app — and the fourth paragraph says what adding somebody to a group DOES share, because a promise that omits the exception is not a promise.

Restore purchases must say what happened, whichever of the four things happened. It used to hand the promise straight to the Pressable, so three of the four outcomes produced nothing on screen: no message, no busy state, no change. App Store review requires the control; one that answers in silence is the same as not having it.

The version is read from the build, not typed in. It said v1.0.0 while the app shipped 1.0.3, which makes a bug report point at the wrong build.

The appearance choice is stored on this device only, and says so.

Related

• balances
• plans
• recurring
• delete-account
• pro-never-gates-the-core-loop

Sources

• src/app/account.tsx
• src/hooks/use-appearance.tsx