Repository navigation
Mobile / small-screen support: current state and a phased proposal #1371
Replies: 3 comments
|
@abouolia would appreciate your thoughts on whether small-screen support is something you'd take contributions toward, and whether the phasing above looks right. Happy to start with the Phase 1 dialog/drawer breakpoint PR if there's interest. |
|
Following up with a concrete plan — design guidelines + a PR-sized backlog for taking the whole webapp responsive without a rewrite (additive Desktop ( Part 1 — Design guidelines1.1 Breakpoints
Single source of truth in SCSS ( 1.2 Touch targets
1.3 Action hierarchyEvery screen/dialog/form declares its actions in one of four roles. The role
Rules:
1.4 Dialogs → sheets
1.5 Data tables → cards
1.6 Navigation
1.7 Forms
1.8 Typography & spacing
1.9 Interaction
1.10 Definition of done (per page)
Part 2 — BacklogOrdered. Each item is intended to be one reviewable PR. Epic A — Foundation
Epic B — App shell
Epic C — Dialogs & drawers
Epic D — Forms
Epic E — Per-page passes
|
|
@abouolia — a friendly check-in rather than another proposal. Over the last few days, while self-hosting Bigcapital for a real client bookkeeping migration, I've opened a handful of things:
I don't want to flood the tracker or nudge the project somewhere you don't want it to go. Would contributions along these lines be useful to you — and if so, is there a shape you'd prefer (discuss-first vs. small PRs, areas to leave alone)? Or would you honestly rather I just keep this on our fork? Totally fine either way — you have the roadmap and I don't. Either way, thanks for building this, and for the fast turnaround on the invite-accept fix a few days back. |
Uh oh!
There was an error while loading. Please reload this page.
Summary
The Bigcapital webapp has effectively no responsive / small-screen support. On a phone, the public auth pages (login, forgot password, reset) work fine, but every screen behind login requires horizontal scrolling and pinch-zoom, and modal dialog actions frequently render off the right edge of the viewport where they can't be tapped at all. This makes routine admin tasks — e.g. re-sending a pending user invitation from Preferences → Users — impractical from a phone.
I couldn't find any existing issue or discussion tracking this, so this is a scoping proposal before any PR.
Evidence (from a current
developbuild)index,PrivatePages,AuthenticationPage), there is exactly one media query:(forced-colors: active)for high-contrast mode. There are zero width/viewport breakpoints anywhere in the application CSS.flexboxgridis loaded but not used for reflow.<meta name="viewport" content="width=device-width, initial-scale=1">is present and correct — so the problem is purely layout CSS, not viewport config.What breaks behind login
Dialog,Drawer) render at fixed pixel widths. On a narrow viewport the dialog overflows and its footer action buttons (Save / Submit / Invite / Resend) sit off-screen to the right — often unreachable even with horizontal scroll inside the dialog.react-table) have no mobile treatment — no horizontal scroll container, no column collapsing, no card view.The "re-send a user's invitation" flow hits #2 and #3 at once (a table row menu that opens a dialog), which is why it's close to impossible on a phone.
Proposed phased approach
Rather than a full redesign, a pragmatic sequence that delivers usable mobile access to the existing UI:
Phase 1 — Dialogs & Drawers go full-screen on small viewports.
A single breakpoint in the app's own SCSS: at
max-width: ~820px, make.bp*-dialog/.bp*-drawerwidth: 100vw; max-width: none; margin: 0, pin the footer, and let footer button rows wrap. This alone unblocks every create/edit/invite/resend flow. Small, low risk, no component changes. I'm happy to open this PR first.Phase 2 — App shell.
Collapse the sidebar into an off-canvas drawer below the breakpoint; make the top bar and content area fluid.
Phase 3 — Data tables.
Wrap tables in an
overflow-x: autocontainer at minimum; optionally a stacked/card layout for the most-used lists (Users, Invoices, Bills, Expenses).Phase 4 — Pass over remaining fixed-width containers (Preferences panels, financial report viewers) for fluid widths + touch target sizing.
Questions for maintainers
Happy to start with the Phase 1 dialog/drawer PR immediately if there's appetite.
All reactions