Guide
Read-only mode
Existing transactions open as static labels instead of editable fields — tap Edit to change them. A v13 feature for safer browsing.
Since v13, Bluecoins opens an existing transaction in a read-only view by default. Instead of a form full of editable fields, you see the entry rendered as static labels — nothing changes until you deliberately tap Edit. New transactions always open directly in edit mode.
What the read-only view shows
The whole form is re-rendered as a clean summary:
- Amount — shown large, signed, and color-coded: red for expenses, green for income, blue (absolute value) for transfers, and the default color for zero.
- Category and account — static text with icons instead of tappable pickers.
- Date and time — static text with a calendar icon.
- Labels — shown without remove icons or an “Add” button.
- Split transactions — each split row renders as static text with a vertical divider bar; add, clear, and running-total controls are hidden. Split amounts are signed and colored like the main amount.
- Transfer fee — rendered read-only, negative, and in expense red.
- Attachments — the add-attachment button is hidden and attached files show no delete control.
- Title bar — shows the transaction type (Expense, Income, or Transfer) instead of a blank title.
The intent is a glanceable, uneditable summary you can safely browse — including the entries you reached from a list you were just paging through.
Editing an existing transaction
A single expandable Edit button sits in the bottom bar. Tapping it switches the form into the familiar editable mode with the normal Expense/Income/Transfer toggles and Save button. The toggle is one-way: once you are editing, you stay in edit mode until you save or leave.
Reminders: Record and Edit
For reminders in read-only mode, the bottom bar shows two buttons:
- Record — logs the due reminder as a real transaction.
- Edit — switches to edit mode.
Paging through a list
While viewing a transaction read-only, previous/next arrows let you page through the list the transaction was opened from — each neighbor reloads in place, so you can review a whole batch of entries without returning to the list between each one. The arrows appear only when there is a previous or next transaction to move to.
Why read-only by default
Opening entries as read-only removes the risk of accidentally changing a number while you are just looking — a small guardrail that matters when you are reviewing an account you share with family or checking a statement against the app.