Money,
made clear.

DTB explores how a full banking app can feel calm without hiding the details that matter. Its central idea is simple: make the consequence of an action visible before asking someone to commit.

The concept connects available money, domestic transfers, utility bills, card security and spending records. AI helps interpret intent and explain verified information within familiar controls.

Tunisian digital banking already covers substantial everyday tasks. MyBIAT’s 2026 releases describe dashboard customization and category budgeting. Attijari UP documents card controls and bill payments. La Poste’s D17 and Flouci also address local transfers and bills. [S01–S08]

The opportunity is therefore a design hypothesis about clarity and control, not a claim that Tunisian banking lacks digital functionality. Public documentation establishes task relevance; it does not establish how people experience those tasks.

I reviewed public official product pages, release notes and bank-published store descriptions on 18 October 2026. The benchmark includes six Tunisian offerings and four international references. International patterns inform communication; they do not imply Tunisian eligibility or product feasibility.

D means documented in the reviewed material. ? means unverified—not absent. Authenticated app navigation, interaction quality and accessibility were not tested.

These personas are provisional scenario models generated to explore contrasting needs. They are not interview participants, observed behavioral segments or validated market profiles. Financial capability and digital confidence are not inferred from age.

Yasmine anchors every app screen and financial record. Nader and Amel provide alternative lenses for evaluating the same concept; the interface does not silently change account holders between screens.

Working problem: when checking money, authorizing a payment or responding to uncertainty, a customer may have to reconstruct what is available, what an action costs and whether it actually happened. DTB tests whether those consequences can share a clearer visual and task structure.

Prioritization uses a consequence-first framework: protect money and access, support frequent domestic tasks, then add optional interpretation. Reach and effort are unknown, so a numerical RICE score would suggest unsupported precision.

Home, Payments, Cards, Insights and Profile stay in the same order. Search sits above that structure as a route into existing features. It never becomes a separate conversation that must be understood to use the account.

The diagrams show proposed experience logic. They are not results of card sorting, tree testing or behavioral observation.

The grayscale collection uses a consistent 393 × 852 viewport, 24 px side gutters and a 4 px spacing unit. Each wireframe maps one-to-one to its final screen ID. These are structured static layouts; visual completeness does not establish usability.

Dashboard A keeps money in a stable position. Dashboard B moves the upcoming bill above it. Review A groups the financial consequence into one scan path; Review B gives explanatory context first. A is the proposed direction for both, pending comparison with participants.

Every interface uses English, the same five-tab navigation and the same fictional account holder, Yasmine Ben Ali. TND values retain three decimal places. All merchant events, fees, payment timings and references are synthetic.

Scenario S0: Everyday availability TND 8,420.450 + Savings TND 3,200.000 = total holdings TND 11,620.450. Each walkthrough restarts from S0. The transfer and bill branches are independent.

DTB’s primary model is a conventional banking interface. Assistance interprets a phrase, proposes a route or explains known information. It cannot invent balances, fees, processing times or statuses, and it cannot authorize or silently execute a payment or security change.

The three-payment search total is calculated from matching source rows. The model may propose the filter; the financial calculation is deterministic.

The output is a visual concept with public-source grounding. No usability outcomes or business improvements have been measured. Static screens cannot validate task completion, functional accessibility, security or system reliability.

The proposed first study is a moderated concept-comprehension review with eight English-speaking Tunisian banking users. Functional task and assistive-technology testing would require a later, separately scoped prototype or implementation.

DTB turns a broad banking brief into a connected visual system: 48 matching wireframes and final screens, six flows, four journey maps, a coherent identity and five sequential walkthroughs. Its strongest proposal is the continuity between a decision, its authorization and its confirmed consequence.

The unanswered questions are consequential: whether these labels match users’ mental models, whether optional assistance improves findability, whether confirmations add useful assurance, and whether local partners can deliver the status and control model reliably.