> ## Documentation Index
> Fetch the complete documentation index at: https://docs.regasolutions.io/llms.txt
> Use this file to discover all available pages before exploring further.
# REGA on your phone
> What REGA becomes below 900 px wide: what disappears, what you cannot do there, and how to split the work between your computer and your thumb.
On a computer, REGA is a three-column command post: you watch a stream. On a phone the question is no
longer the same — it is **see a drop and buy with your thumb**. The interface does not merely shrink:
it **chooses** what it gives up, and the order of those sacrifices is not left to chance.
**The rule that governs this whole page: what informs gives way, what acts stays.** A counter, a
label, a screen title, a context reminder — all of that falls. A switch, a price, a `BUY` button —
never. The `BUY` button does not shrink at any point: on a phone it even gains a whole row, across
the full width of the card.
***
## The four widths
REGA knows four layouts, and they trigger on the **width of the window** — never on the type of
device. Each tier keeps everything the previous one has already removed.
```mermaid theme={null}
flowchart TD
A["1580 px and above
Three columns, everything visible at once"]
B["1280 px and above
Purchases and conversations move
behind the ⋮ button"]
C["900 px and above
The sidebar becomes a rail of icons
Settings move behind the ☰ button"]
D["Below 900 px — PHONE
Tab bar at the bottom · one single column
Targets raised to 44 px · menus and windows
come up from the bottom · one single layout"]
E["Below 430 px — narrow screen
The logo falls · the word AUTOBUY falls
The account name is shortened"]
F["NEVER FALLS
The AUTOBUY switch and the paying account
— the only two things that touch money"]
A --> B --> C --> D --> E --> F
```
| Window width | What changes |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **1580 px and above** | The full layout, three columns. |
| **1280 – 1579 px** | The right column — recent purchases and conversations — becomes a panel you call up with `⋮`. |
| **900 – 1279 px** | The sidebar shrinks to a 64 px rail of icons; the left column becomes a panel you call up with `☰`. |
| **Below 900 px** | **The phone tier.** No more sidebar: a fixed 56 px tab bar at the bottom. The header goes from 56 to 52 px. Every touch target goes from 32 to **44 px**. |
| **Below 430 px** | One further compaction of the header. This is **not** a fifth tier: nothing else in the product changes. |
**The tiers are pure width, and that is deliberate.** An iPad held in portrait (744 to 834 px)
therefore gets the phone layout — bottom tab bar, single column — on a screen more than 1000 px tall.
Target size, on the other hand, does not follow the width but **the finger**: every touch screen gets
its 44 px targets, including a 1024 px iPad Pro that is not in the phone tier at all.
***
## Navigating with your thumb
The sidebar disappears entirely, and seven navigation entries do not fit under a thumb: at 390 px they
would be 55 px each, below the minimum touch target, and nobody would read their labels. So REGA keeps
**four**, plus a fifth button that calls up the rest.
| Tab | What you do there |
| --------- | ---------------------------------------------------------------------------------- |
| `Feed` | The live stream: listings the second they are born, and the `BUY` button. |
| `Filters` | What the radar is looking for on your behalf. |
| `Orders` | Your orders, the conversations, the parcels at a pick-up point. |
| `Tracked` | The watchlist — items set aside, and their prices. |
| `More` | Opens a `NAVIGATION` sheet containing `Accounts`, `Sales`, `Stats` and `Settings`. |
Inside the `More` sheet, every entry **gets its full label back** — it is no longer an icon to guess
at. If you often go to Sales or Accounts, that is two gestures instead of one: on a phone those are
the screens you consult, not the ones you act from in a hurry.
On the screenshots in this page, an `Administration` button takes up room in the header. REGA staff
only — this button does not appear on your account. In practice your header has **52 px more room**
than the images show: that is exactly the width of that button and its gutter, and at 390 px it makes
the difference between a readable account name and a truncated one.
***
## What disappears from the header, and why
The header is the most contested surface in the product: at 390 px it overflowed by **79 px** before
it was reworked (and by **149 px** on a 320 px screen). Here is what gave way, in order.
**Below 900 px**
| What falls | What stays in its place |
| ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| The `RADAR ACTIVE` label | The green dot. It says the same thing without costing any width. |
| The account's scope label | **The account name** — that is what tells you who pays. The full scope stays in the tooltip and on the Accounts screen. |
| The words `Vinted` and `Vestiaire` | The coloured pill, which already carries the marketplace. |
| The rotation count (the "2/3") | It stays intact on the Accounts screen. |
| The account avatar | The name is written right next to it: the avatar was a repeat. |
**Below 430 px**
| What falls | What stays in its place |
| ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| The `rega` logo | The tab bar already names the current screen. |
| The word `AUTOBUY` — **130 px measured**, the biggest consumer in the bar | **The switch, its colour and its state.** A screen reader still hears the full word. |
| The text of the second marketplace | Its pill. A missing half would suggest a disconnection. |
| An over-long account name | It is shortened with an ellipsis, with a **56 px** floor — a truncation you can see beats a silent one. |
**Two elements fall at no width at all: the AUTOBUY switch and the indicator of the account that
pays.** They are the only two elements of the shell that touch money. Everything else is negotiable;
these two are not.
***
## Screen by screen
### The feed
Below 900 px, **the layout is imposed**: `Wall` and `Table` are not offered. If you look for them,
REGA answers `On a phone there is only one layout.` And for a second feed side by side:
`Only one feed on this screen — two bands would fall below the readable card width.`
This is not a punishment: it is where the phone **takes back** what the old compact card used to
withhold. The photo goes from about 128 px to a far larger block, and the thumbnail carousel returns.
That thumbnail rail used to be hidden while the images were already loaded: measured at **0 visible
rails out of 10** at 890, 555 and 390 px, while the card announced 4, 5, 7 and 8 photos. We were
paying for the download and showing nothing.
What the card gives up, and where to find it again:
| Given up on the card | Where it stayed |
| ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| The secondary facts — triggering filter, condition, country | On the item's detail sheet, all of them. |
| The paying-account label | Written **once** in the band header. Repeating it on every card of a screen that only shows two is pure noise. |
| The estimated delivered total | The price stays large: that is the figure you decide on. |
| The stream rate | In the `☰` panel (`Account, autobuy and feed settings`). |
**Scrolling the feed freezes it.** Forty pixels are enough — and on a phone, scrolling is the default
gesture. That is intentional: we do not want the list moving under the thumb aiming at `BUY`. The
freeze announces itself with a sticky `NEW` banner preceded by the count; tapping it puts the list
back at the top. **Exception: when AUTOBUY is armed, the feed no longer freezes** — the machine buys,
the human is not aiming.
### Filters
* Below 1280 px: the heading of the autobuy column falls, **the switch stays**.
* Below 900 px: the detections counter falls (it informs); the grid drops to one column; the header
actions take the full width.
* **Below 599 px: the row summary and the filter's cap disappear too.** The name, the autobuy switch
and the `⋯` never fall.
* Every settings window sticks to the bottom of the screen and reserves room for the phone's home bar.
Creating or reworking a filter from a phone is possible, but it is the least comfortable gesture in
the product: the window is tall, it scrolls, and the filter's cap — the only money bound that really
follows automatic buying — is no longer readable on the row at that width. **Build your filters on a
computer, use them from your phone.**
### Orders
This is the screen that gained the most from being measured. When wrapped, the sticky toolbar took up
**310 px out of 736 — 42 % of the screen, permanently**, because five view chips fell onto three lines
and nine status chips onto five. Today each row **scrolls in place**. What is left of it: 154 px,
18.2 % of the screen.
* An order row goes from 4 rows to 2, with a 40 × 50 thumbnail.
* **The Kanban stacks**: at 390 px with 40 orders it showed only **1.19 column out of 8** at a time,
and 32 % of the stack. It is now presented one column per row.
* The conversation thread becomes a panel you call up, instead of a column.
* Below 700 px, the link to a pick-up point's map falls — **the parcel count and the waiting marker
stay visible**, they are the only two pieces of information that decide whether you travel. It is
the address that gets abridged, never them.
### Tracked
* **The layout selector is not rendered at all.** `Grid` needs 760 px, `Table` needs 1100: at 390 px
only `List` would remain, and a selector with one entry is a dead control. REGA does not hide an
unavailable option: **it does not offer it.**
* If you shrink the window below the floor, the display falls back to `List` **without erasing your
choice**: it returns as soon as the room returns.
* Brand, category and price bounds move behind a `Refine` button, whose tooltip reads
`Brand, category and price bounds`. When filters are active, it gives their number.
* The card goes from 7 rows to 3. **Nothing is removed: what was stacked is laid side by side.**
Before, the row was 221 px tall and you could see **one single item in full, out of fourteen**; you
now see three.
### Sales
This was the screen most damaged at small widths: at 390 × 844, **0 whole cards out of 16** were
visible, because the header took 494 px out of 736 scrollable — **60 %**. After the rework: **2 whole
cards**. The photo stops being portrait and becomes square (in 4/5 portrait it cost 212.5 px on its
own); the context block goes from 148 to 62 px.
Below 560 px, a sentence **appears** above the table: `◂ the table scrolls sideways ▸`. It is hidden
everywhere else, and shows up only at the width where the overflow is real.
### Accounts
**This is the only screen that becomes a master-detail.** On a phone, only one of the two columns is
on screen at a time: the list, or the sheet. The other is not removed — it is one arrow away,
`←` `Back to the list`.
The two marketplace doors (Vinted, Vestiaire Collective) stack below 719 px: a half-width door on a
phone becomes a target you miss. And a group's member list is capped at 48 % of the screen height —
otherwise it would stop you reaching the save button.
### Stats
The **screen title disappears**: the navigation bar already says where you are, and it cost a whole
row on the screen that has the fewest left. The only remaining landmark is the active tab at the
bottom. Every row of chips is gathered onto one single scrolling line — measured: 336 px, then 290 by
putting each group on its own row, then **\~200** by gathering them.
### Settings
This is the most important screen to know from a phone, because **three things exist only there**:
the language, the purchase ceiling, and switching alerts on for this device. Confirmation actions
switch to a full-width column, with the cancel option **above** the irreversible one: under a thumb,
position matters more than colour.
***
## Menus, windows and targets: what changes everywhere at once
These three rules apply on **every** screen as soon as you are on a touch screen or below 900 px. They
explain most of the surprises.
A `⋯` menu, a selector, a list of choices: everything opens **stuck to the bottom of the screen**,
where the thumb is — never underneath the button you just tapped.
Full width, rounded at the top, capped at 92 % of the height, **and with their own internal
scroller**. Without that scroller, everything overflowing was physically out of reach — measured:
1337 px of content inside a 791 px window, and nothing scrolling.
Filter chips and fields measured at **31 and 32 px** on a 390 px iPhone: raised to 44. Targets that
are too small are enlarged **by their sensitive area, not by their drawing** — the screen does not
get bigger, it gets touchable.
A page's primary button takes the full width — but **no further**: measured on an 820 px iPad, a
752 px button is no longer a target, it is a bar.
***
## Money, from a phone
This is the section to read twice. Nothing that follows depends on screen size, but all of it takes on
a different meaning there — because a phone locks, goes into a pocket, and loses signal.
Arming the `AUTOBUY` switch from your phone arms **the server**. It survives closing the tab,
closing the browser, switching the device off. The line `Where automatic buying runs` —
`on our servers — closing the tab does not stop it` — **states that fact**; it is not a switch you
set. **The only gesture that stops it is disarming it.**
`Purchase ceiling` (Settings → `BUYING`) applies to **every** purchase, manual and automatic, on
every machine — `Above this amount, the purchase is refused and you are told. Empty = no ceiling.`
It is **empty by default**, and once set it also refuses an item whose price cannot be read. ·
`Cap per item` lives in the dashboard's AUTOBUY panel, is **120 €** by default and is
**remembered only in that one browser**. · A **filter's** cap only bounds that filter's automatic
buying.
`Automatic pick-up point` (Settings) is **on by default**, and its text is blunt: `rega chooses
the collection point during the purchase. Turned off, the purchase fails for want of a pick-up
point — leave it on.` Turned off, the purchase fails with
`No pick-up point could be selected for this order.` — **nothing asks anyone anything.** That is a
different thing from `PREPARE THIS CARRIER` (Accounts screen), which is a REAL purchase of a few
euros, once per account and per carrier, and which remains **optional**.
If the connection drops **at the moment of paying**, the outcome is unknown: replaying would risk
a double charge. So REGA does not replay. On a phone — a lift, a train, a bad signal — this is the
case that will happen to you. **The move: open `Orders` and look, before retrying anything.**
**`Cap per item` does not travel.** It is remembered in the browser where you set it: the value set on
your computer does not exist on your phone, and vice versa. If you want a bound that applies
everywhere and to everyone, that is the `Purchase ceiling` in Settings — and to bound an automatic
purchase, it is the filter's cap.
The gain from `PREPARE THIS CARRIER` is about 1.3 s on the purchase, and it **is not additive**: it is
the **seller** who picks the carrier. Preparing several widens the **share** of your purchases that
gain that time; it never increases the gain itself.
***
## Drop alerts: the only chain that matters
A phone without alerts is just one more screen. Here is the complete chain, and the two places where
it breaks in silence.
```mermaid theme={null}
flowchart TD
F["A filter with “Notify me” ticked"] --> R["The radar detects the listing"]
R --> C["🔔 The bell, inside the application"]
R --> P["An alert pushed to your devices"]
P --> D{"Is this device switched on?
Settings → Notifications"}
D -->|"no"| X["Silence — and nothing tells you"]
D -->|"yes"| I{"iPhone?"}
I -->|"opened in Safari"| S["Announced REFUSAL:
rega must be added
to the home screen"]
I -->|"added to the home screen
or Android"| N["System alert:
photo · brand · title · price"]
```
This is the most forgotten switch, and REGA says so itself:
`Only fires for the filters that asked for it — the switch lives on each filter.`
Its help text, inside the filter window: `One notification on every detection by this filter —
photo, brand, title and price. No cap is applied: a wide filter will produce a lot of them.`
Settings → `Notifications` → `This device` → `Switch on for this device`. The button
`Asks the browser for permission, then registers this device.` The state you want is
`Device switched on ✓`. Every phone, every computer is switched on separately.
From a plain Safari tab, REGA refuses and tells you why: `On iPhone, alerts require adding rega to
the home screen (Share → Add to Home Screen), then opening it from there.` Do it, then reopen REGA
**from the icon**.
Settings → `DEVICES AND CONNECTIONS`. The `Mode` row must read `Installed on the home screen` and
**not** `Browser tab`. The `Alerts` row must read `Allowed`.
**There is no rate floor on alerts, deliberately.** You choose which filters notify, so you choose the
volume. An unmanageable flow always comes from a filter that is too wide, never from a missing
setting.
***
## What you cannot do from a phone
Said plainly, so you do not go looking for it.
| Not possible | Where to do it |
| ---------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| Choose the feed layout (`Wall`, `Table`) | On a wider screen. `Table` needs 1280 px. |
| Open two feeds side by side | From roughly 690 px of width — an iPad in portrait opens two. |
| Choose the watchlist layout | `Grid` from 760 px, `Table` from 1100 px. |
| See the account list **and** a detail sheet at the same time | On a computer. On a phone it is one or the other, one arrow apart. |
| See the stream rate on the feed screen | It is in the `☰` panel. |
| Change the language from the header | Settings → `APPEARANCE`. That is now **the only** place. |
| See brand / category / price bounds of Tracked without a gesture | They are behind `Refine`. |
| Receive an iPhone alert from a Safari tab | Add rega to the home screen (see above). |
| Make useful use of the `⧉` detached-window button | It is there, but it asks for a 560 × 980 window that a mobile browser ignores. |
***
## Splitting the work
The right way to use REGA is neither “everything on the phone” nor “everything on the computer”. It is
a split, and it follows directly from what each width can do.
```mermaid theme={null}
flowchart TD
Q{"What are you doing?"}
Q -->|"I want to see and buy now"| T["PHONE
Feed · Tracked · Orders
Arm or disarm AUTOBUY"]
Q -->|"I am building or refining my strategy"| O["COMPUTER
Filters · caps · groups
Accounts and pick-up points"]
Q -->|"I am comparing, deciding, doing the books"| O2["COMPUTER
Sales · Stats · the Orders Kanban"]
T --> A["Automatic buying itself
runs on our servers
in both cases"]
O --> A
O2 --> A
```
| On the phone | On the computer |
| --------------------------------------- | ----------------------------------------------- |
| See the drops and buy with your thumb | Create, name and refine the filters |
| Arm / disarm `AUTOBUY` before going out | Set the caps and the buying scopes |
| Track an item, answer a seller | Compare many sales at a glance |
| Check an order, a pick-up point | Read the Orders Kanban across its eight columns |
| Receive the alerts | Connect the accounts, prepare the carriers |
***
## Our advice
On iPhone it is **mandatory**: without it, alerts do not exist — Safari only grants them to an
application added to the home screen. Everywhere else it is still the right setting: the
application opens full screen, room is reserved for the notch, and the header no longer slides
under the status bar. Then check in Settings → `DEVICES AND CONNECTIONS` that `Mode` reads
`Installed on the home screen`.
The filter (`Notify me`), the device (`Switch on for this device`), and the alert type. Forgetting
one gives you a **silence you cannot diagnose** — and then you believe the product is broken. If
you hear nothing, go back over all three in that order before any other hypothesis.
There is no rate floor whatsoever. A wide filter set to notify, on a phone, produces a flood you
will end up muting at system level — and you will mute the alerts that mattered along with it.
Keep the wide filter **in the feed**, and reserve alerts for filters where every detection
deserves your thumb.
First the obvious one: buying runs on our servers, you can lock the screen and pocket the phone.
Then the detail nobody guesses: **when armed, the feed no longer freezes on scroll**. That is
exactly the right “watching while walking” mode — disarmed, forty pixels of scroll are enough to
freeze the list.
At 390 px, a 23-character name put **15 px of the name outside the window**; with two marketplaces
(Vinted + Vestiaire) at 320 px, the Vinted name shrank to 18 px. The floor is now 56 px, and a long
name shows in full from 768 px upwards — but on a phone, a short name is the only way to read
**who pays** without opening the tooltip.
The dashboard's `Cap per item` does not follow you from device to device: set on your computer, it
does not exist on your phone. The bound that applies everywhere is the `Purchase ceiling` in
Settings; the one that bounds an automatic purchase is **the filter's cap**
(`Cap per item — leave empty to impose no cap`). Set them from the computer, once.
This is counter-intuitive: `Compact` **is not more compact** on a phone. The phone tier already
gives 12 px margins, and the compact setting gives back 14 — so wider. The setting that really
changes density is `Text size`: its three steps are 0.94, 1 and 1.08. `Compact` —
`More listings on screen` — is the right choice if you want to see more cards.
On a phone, a `⋯` or a selector opens **at the bottom of the screen**, never under the button.
This is not cosmetic: it is what removed truncated menus, where entries fell outside the frame and
became unreachable. And if a window looks cut off at the bottom, **it scrolls internally** — put
your finger inside it, not on the page.
The language follows **the person**, not the device: chosen on your computer, it catches up with
you on your phone when you open it. It also governs your e-mails —
`The interface, the messages and the e-mails.` It is in Settings → `APPEARANCE`, and nowhere else.
`PREPARE THIS CARRIER` is a real purchase of a few euros, once per account and per carrier. It is
**optional**: without it the purchase still completes, simply \~1.3 s slower. Do it on the Accounts
screen, calmly — on a phone it is a master-detail, one sheet at a time, and the `←`
`Back to the list` arrow brings you back.
***
## What surprises people
The tiers are pure width. An iPad in portrait (744 to 834 px) therefore gets the bottom tab bar and
the imposed layout — on a screen more than 1000 px tall. That is deliberate. It does, however, open
**two** feeds side by side, where a 390 px phone only opens one: the calculation is on the real
width, not on the tier.
Because **the touch target does not depend on the width, it depends on the finger**. This was a
defect measured on the bench: on an iPad Pro in portrait, targets stayed at 32 px — mouse size.
Every touch screen now gets 44 px, whatever its width.
It is not folded away, it is not abbreviated: it is gone. The only landmark is the active tab in
the bottom bar. That is a choice: this title cost a whole row on the screen that has the fewest.
Below 430 px the word falls: 130 px measured, the biggest consumer in the bar. A switch is read
from its position and its colour, not from its label — and the label comes back at 431 px. A screen
reader still hears the full word: we lighten the eye, not the accessibility.
With Vinted **and** Vestiaire, below 430 px, the second half of the indicator loses its text and
keeps only its coloured pill. **This is not a disconnection.** A missing half would make you
believe the marketplace is not connected: it gives up its text, never its presence.
It is rendered at every width, phones included, and its tooltip reads
`Open the general stream in a detached window`. It asks for a 560 × 980 window — a mobile browser
ignores those dimensions. Do not count on it from a phone.
On a card the two do not collide: a horizontal swipe turns the carousel **without** scrolling the
page. In the full-screen viewer, **every** gesture turns a photo and the page does not move. That
is intentional.
It is the only red mark in the product, and it is placed so as not to cross a confirmation message.
If something is wrong, that is where to look — not at the top of the screen.
***
## The limits, said plainly
**Landscape mode is not handled.** Widths alone decide: an iPhone turned sideways (844 px wide) stays
in the phone tier, with its 56 px tab bar and its 52 px header on a 390 px height. No measurement of
that case exists in our records. Hold your phone in portrait.
* **Sales caps out at 2 whole cards** at 390 × 844. Four is out of reach without amputating the photo.
To compare many sales, it is the same page on a wider screen.
* **On a 320 × 700 screen, the watchlist shows only one card at a time.** Two remedies were tried and
measured: 384 px of free height remain, and two cards need 400. We preferred not to amputate
anything.
* **Below 480 px, a seller's review count disappears** (their username stays). The threshold is on
screen width and it is an acknowledged stopgap: depending on the width, the seller card goes from two
columns to one, so the username survives at 360 px and dies at 390.
* **The Vestiaire page is not linked from any navigation** — not on a phone, not anywhere.
What is verified, on the other hand: across the **nine pages** of the product, at 390, 834, 1280 and
1440 px, in French and in English, **no horizontal overflow**. The page never slides sideways under
your finger.
***
## Going further
The detail of every control in the feed, and what can refuse a purchase.
Building a narrow filter — the kind that deserves an alert on your phone.
The orders, the conversations and the parcels at a pick-up point.
Purchase ceiling, automatic pick-up point, notifications, language, devices.
Who pays, and how to prepare a carrier.
What the `Refine` button does, and what the displayed prices are worth.