UI Research for Sarion: Towards a Mature Design

Over the past few months, I’ve focused much of my time on Sarion, my personal assistant project built as a true MVP: functional, tangible, but deliberately minimal visually.

During the initial phase, there was only one priority — making everything work. The UI was created quickly, without formal design training, but with the goal of validating the functionality.

Now that the project has reached a certain stability, it’s time to take the interface to the next level: turning it from “usable” to “pleasant to use,” without losing the speed of development that defines it.

To do this, I’ve started an in-depth research on the best UI solutions for note and task management, analyzing many sources including design systems, industry blogs, and case studies of real applications.

This is not yet a redesign phase, but one of study and observation — a moment to understand before touching code or layout.

What I’m Trying to Understand

At this stage, I’m not designing new screens: I’m looking for patterns that actually work.

The goal is to identify the most solid best practices used by mature productivity products — like Notion, Obsidian, Todoist, and Jira — and understand how to adapt them to a context like Sarion.

From my research, some clear directions are emerging:

• Card-based layouts as the dominant structure for note and task management
• Minimal design to reduce cognitive load and improve readability
• Clear hierarchical navigation, with breadcrumbs and collapsible sections
• Advanced search and filters, because productivity relies on finding information quickly
• Responsive design as a prerequisite, not an option
• Accessibility integrated, not added afterward

These elements consistently appear in authoritative references such as Material Design, Apple HIG, Atlassian Design System, and Nielsen Norman Group guidelines.

Why This Phase Is Crucial in an MVP Lifecycle

When building an MVP, the temptation is always to consider design a “later” concern.

But every MVP that survives its first user interaction must eventually face a critical step: moving from a product that works to a product people enjoy using.

In this sense, the UI research I’m conducting now is an integral part of Sarion’s growth journey.

It’s not about redesigning everything: it’s about understanding what to improve, where to intervene, and which principles to maintain.

What I’ve Already Discovered So Far

Here are some preliminary conclusions — insights I’m validating that will directly influence Sarion’s next iterations:

Card-Based Design Is a Winning Constant

The most effective productivity apps — from Notion to Trello — organize content in cards.

This approach helps segment information, facilitates visual scanning, and naturally adapts to responsive layouts.

Minimalism Works (When Thought Through)

A “clean” interface isn’t an aesthetic choice, but a strategic decision.

Google and Nielsen Norman Group have shown that users perceive simple, consistent designs as more reliable and usable.

The next step for Sarion will be reducing the unnecessary and letting the content take center stage.

Navigation Must Be Hierarchical and Predictable

As features increase, a clear structure is needed.

Breadcrumbs, collapsible sections, and consistent labels help users avoid getting lost — a point I plan to address soon.

Search and Filters Are the Heart of Productivity

Every successful note or task management app has intelligent search that understands context and intent.

I’m already exploring ways to integrate autocomplete, dynamic filters, and result highlighting.

Responsive and Accessible Are Not “Features”

In 2025, non-accessible design is no longer acceptable.

The new WCAG 2.2 standards provide clearer rules on focus, contrast, and alternatives for drag-and-drop interactions.

Implementing them is not just an ethical matter, but a real usability improvement.

(crediti: Figma)

The Next Phase

In the coming months, I’ll bring this research into practice.

The goal is to translate the studied patterns into a lightweight, modular design system for Sarion — something consistent, documented, and easily expandable.

The first planned changes include:

1. Card layout for notes and tasks
2. Minimalist theme with updated typography and spacing
3. Improved search with autocomplete and filters
4. Mobile and tablet optimization
5. Full accessibility review according to WCAG 2.2

It’s a process that will require time and experimentation, but it marks the beginning of the maturity phase for my MVP.

Conclusion

The UI research I’m conducting isn’t an academic exercise, but a natural step in the evolution of a project born as a technical experiment and grown into a real product.

Just as the structure of workflows made Sarion more controllable and scalable, a clear and modern design system will make it more pleasant, coherent, and ready for broader growth.

I’m learning that in web design, maturity doesn’t come from a sudden redesign, but from a deep understanding of what really works — and the patience to improve one decision at a time.