Making text bigger in a notes app sounds like one setting. In real use you hit a conflict: buttons, lists, and settings copy are too small and should grow; the body you’re writing already feels right, and enlarging it reduces how much you see per line. Conversely, wanting a larger body doesn’t mean sidebars and dialogs should all grow with it.
That’s why Abox Note offers two independent settings: interface font size and editor body font size. You can make the app’s chrome clearer while keeping the body compact—or keep a compact UI and only enlarge long prose.
Interface text helps you recognize the software; body text helps you read and organize your own content. Tying them together saves one control—and mixes two problems into one answer.
Seeing the tool vs. seeing the content
Interface text lives in note lists, menus, settings pages, and dialogs. It’s usually short, and it works with icons, spacing, and button sizes. Adjusting it is about recognizing action entry points more easily.
Editor body might be a long essay or a flash of one idea per line. Font size directly affects characters per line, how many paragraphs fit on screen, and the rhythm of long reading sessions. Some people want a larger body; others care more about information density.
If both share one value, every tweak moves the whole UI. Enlarge to see the sidebar and you lose body lines; shrink the body to see more lines in a small window and settings copy and the note list become harder too.
So the question isn’t “what size should the whole app use,” but “which reading difficulty is this adjustment trying to fix?”
How the two settings work
Abox Note places both controls next to each other in settings:
- Interface font size affects lists, settings, dialogs, and other chrome;
- Editor body font size affects note content and line numbers.
Each setting is saved separately. Changing interface size doesn’t quietly rewrite how note body typography feels; when you change body size, line numbers follow so they don’t drift out of alignment with larger text.
Desktop and mobile don’t share the same interface density, so defaults can differ. Once you’ve chosen, your settings win. The body has its own default and doesn’t have to track the chrome.
That split also makes outcomes easier to predict: to see buttons clearly, adjust the interface; to change writing density, adjust the body.
After splitting, keep the boundary restrained
One more control is one more choice to understand. The first time someone sees “interface font size” and “editor font size,” they may need one try to feel the difference; a few areas with their own typography may not auto-adapt from interface scaling alone.
The answer isn’t infinite splitting. If sidebar, menus, titles, and code blocks each had their own size, settings would become a burden again. Abox Note currently splits only the most obvious two layers: app chrome and note body.
That boundary fits a long-form writing tool, because chrome text and content text do different jobs. If an app only has a little short copy and no sustained reading or editing, one unified size may be simpler.
Fewer settings doesn’t always mean less burden
Interface size answers “can I see the tool easily”; editor size answers “what density do I want for reading and writing.” Both concern readability—they aren’t the same question.
Forcing both goals into one setting only hides the choice from the settings page into every session’s compromise. A truly simple setting isn’t the one with the fewest options—it’s the one where each option maps to a need you can name.