A Smoother Browser UI
Arivu's embedded browser interface is calmer, easier to recover from, and faster on repeat visits.
We spent this session tightening the browser UI that ships inside the self-hosted Arivu app.
The work was not about adding a flashy new feature. It was about making the existing interface feel more dependable: easier to sign back into, clearer when something goes wrong, calmer to look at, and faster after the first load.
Better Account Recovery
The account screens now handle recovery and invited-user entry points more directly. If you need to get back into your account, the path is visible from the sign-in experience instead of feeling hidden. Invited users also get a clearer handoff into the app.
The form experience is cleaner too. Errors now appear next to the relevant fields instead of only disappearing into a temporary notification. Assistive technologies get stronger status signals for failed actions, while success messages stay quieter.
What this means for you: Account access problems are easier to understand and easier to fix without guessing where to go next.
A Calmer Archive Interface
The embedded UI already had a strong warm-paper archive direction. We kept that personality, but reduced the parts that felt too loud: heavy shadows, intense borders, oversized type, and aggressive contrast.
The result still feels tactile and self-hosted, not glossy or generic. It is simply easier to sit with for longer reading and organizing sessions.
What this means for you: The app keeps its character while becoming less visually tiring.
Faster Repeat Visits
We also measured the shipped frontend assets and improved how the app serves them. The JavaScript and CSS now support browser revalidation, so repeat visits can avoid downloading the full files again when nothing changed.
The missing favicon fallback was fixed too. Browsers now receive a tiny SVG icon instead of accidentally fetching the full app shell as an icon response.
What this means for you: The first load stays small, and later visits waste less bandwidth.
More Confidence Before Shipping
The update includes documented browser checks and regression coverage for the asset caching behavior. We verified mobile layout, form controls, console output, and the repeat-visit transfer path.
That is the standard we want for Arivu: practical polish, measured performance work, and enough automated coverage that small fixes stay fixed.
The direction remains the same: make Arivu powerful, self-hostable, and boring to operate.