Your settings pages are the kind of thing you don't think about until something frustrates you. A form that doesn't behave the way you expect, navigation that makes you hunt for the right page, or inconsistencies that make you second-guess whether you're in the right place.
We've spent time improving the settings experience across Flare. Account, team and project settings all received a new lick of paint. Nothing groundbreaking, just the same kind of polish you find on performance monitoring.
Consistent layout, everywhere
Every settings page now follows the same structure: a sidebar for navigation, clearly grouped sections, and a predictable layout no matter where you are. Whether you're updating your profile, managing API tokens, or configuring notifications for a project, the experience feels the same.
Improved forms and flows
We've revisited the forms across settings to make them more intuitive. Fields are better organised, validation is clearer, and destructive actions like deleting your account or revoking a token are properly guarded with confirmation steps.
Gone are the confusing toggle components on the security and notification pages.
Better navigation
Account settings and project settings each have their own navigation, so you always know exactly where you are.
Small details that add up
Beyond the structural changes, we've cleaned up spacing, typography, and visual hierarchy throughout. Cards have more breathing room. Actions are easier to spot. The overall feel is calmer and more focused.
These are the kinds of changes that are hard to put into a changelog but easy to feel when you use the product.
Give the new settings a look next time you're in Flare. If you have feedback or spot something we missed, we'd love to hear from you.
Continue reading
One core, many clients: the new Flare JavaScript client architecture
We recently reshaped the Flare JavaScript client from a single browser library and a few thin framework specific packages into a small family of packages built on a shared, platform-agnostic core. This post explains why we did it, what the core package exposes, how the browser and Node SDKs are built on top of it, why the React, Vue, and Svelte packages sit one level higher, and how anyone can use the same core to write a Flare JS client for a platform we do not ship ourselves.
Dries
Logging is here!
Logging is now available for all Flare users! Send any log from your app to Flare and use our polished interface to filter and search your logs in real-time.
Jimi
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates
