DEV Community

S.Babas
S.Babas

Posted on Originally published at center.nuxipro.com

The progress and strategies I'm considering for working on NuxiPro

Why redesign now?

Let's be honest: when you're working solo on a project, you rarely have the time (or energy) to bother with complex ergonomics. If a tool takes too much effort to pick up, people just give up.

My goal with NuxiPro was simple: zero friction on a daily basis. I want a fluid, straightforward tool with zero mental load.

To get there without spending months on it, I made a radical decision: delegate the frontend code to the AI while forbidding it from inventing random stuff. I gave it a strict framework based on my own sketches, combined with shadcn/ui. While it handles the visual components, I can keep all my attention where it really matters: the server, the infrastructure, and security.


From paper to component: the Sidebar example

The best way to avoid getting polluted by LLM graphic suggestions is to spoon-feed them with a raw drawing.
A concrete example with the sidebar button: I wanted something minimalist that rotates to switch sides depending on whether the panel is closed or open.

My initial paper sketch
The final implemented design

After a few tweaks with the AI to get it to respect this behavior precisely, the result is clean and exactly as I imagined it.


Global Architecture and Dashboard

For the entire application, same drill: a hand-scrawled global diagram to lock down the panel structure (dynamic zones, workspace lists, etc.), injected into the tool with shadcn/ui.

Global hand-drawn diagram

After a good solid chunk of iterative work with the AI to assemble the building blocks, we end up with this final dashboard:

NuxiPro final dashboard


Behind the scenes: Perf, State, and Security

A nice design is useless if the underlying infrastructure is shaky. Even if this version isn't production-ready yet, I'm actively working on these important points:

  • Settings centralization: Global settings are loaded once from the server as a centralized block. The frontend then splits and distributes the modules cleanly. Result: fewer requests, a clear structure, and a single request sent to the server on change instead of multiple.
  • Client security: It's easy to forget when delegating the frontend, but the client is a potential sieve if neglected. I treated the frontend code with the same level of rigor and security as my server routes and backend.
  • Active security testing: Since I'll be using NuxiPro daily, I want it to be secure, sovereign, and respectful of my users' privacy as well as my own by hosting data in Europe.
  • Design of account security log centralization and monitoring for the server and VPS: To always maintain traceability over transactional actions, account setting modifications, and security logs, crucially without including personal data in those logs, alongside production error management.
  • User account security management: Using magic links for login or sign-up, TOTP (a 6-digit code generated directly on the phone), and passkeys for two-factor authentication.

As soon as a user enables 2FA, they boost their account security with:

  • Passkey: direct connection via the passkey without having to click the magic link.
  • TOTP: activates when logging in with the magic link; you land on a pre-session to enter your code generated by the authenticator app.
  • Backup Codes: sensitive recovery codes to store securely (do not share, otherwise someone else can gain unauthorized access to your account; you can regenerate codes if one leaks to revoke unused ones).

Anyway, the interface is set up, I don't need to touch it anymore. On to the next step.


Why did I choose to move archived tasks to another table dedicated to archives in the database?

Comparison sketch

I made this choice mainly because I don't want to load all useless data, but only immediate useful data.

Let me explain: basically, moving data from the cards table (mainly used to manage the daily kanban and store immediate-utility tasks important for my daily life) avoids loading all tasks. If I hadn't made this separation, all tasks in the "done" column would have stayed mixed with the "to do" and "in progress" ones.

So I want to move these tasks from the kanban table to the archived_cards table, because otherwise I'll run into issues like:

  • Performance issues: related to loading all tasks that are no longer useful on a daily basis. The tool wears itself out trying to load all this useless data.
  • Broken visual design: most software simply hides tasks without moving them. Consequence: this data stays in the background and bloats the software.
  • Visual clutter: your workspace becomes a graveyard of completed tasks, which doesn't make you want to use it, especially if you have to archive manually.

I could have settled for a boolean flag indicating whether a task is archived, but that would only have made things worse by making NuxiPro harder to maintain unnecessarily.

I tested tools that tried to solve this problem without physically moving the tasks (simply hiding them visually without changing anything).

Choosing to physically move the data increases security to prevent leaks, bugs, and immediate crashes if tasks leaked via a simple flag. The archived_cards table is thus designed to grow infinitely and securely, although there are also risks I've taken into account:

  • Potential desynchronisation: I'm assuming it, but I'll test this to assess whether it represents a major risk to anticipate.
  • Write complexity: despite its reading simplicity.
  • Other potential bugs that I haven't detected yet.

In the end, I was able to integrate all this into the project:

  • 2-phase loading: we mandatorily load the lightest data first, then the heaviest data only if the user needs it, otherwise we don't load it at all.
  • Direct local caching of data (tasks, settings, etc.) to avoid reloading them immediately.
  • Server-side centralization of user settings: returning data in a single request without complicating calls.
  • Interface ready to use on a daily basis without unnecessary slowdowns, just the essentials.

The original article is on my blog: https://center.nuxipro.com/en/blog/design-and-server/

Top comments (0)