u/Afraid-Ad4356

Hey guys,

We are currently implementing the backend architecture for our email client. The core focus right now is a system that actively learns from each individual user's behavior and adapts its logic accordingly—learning what you ignore, what you prioritize, and how you work.

While building this out, we had a thought: what if the whole application changes its structure and shape with it as well? Meaning, as it learns about you, the actual UI dynamically morphs to fit your specific workflow (e.g., turning into a Kanban board if you do sales, or an issue-tracker view if you are a dev).

What do you guys think? It sure sounds cool in theory, but will anyone actually pay for an application like this just because it is adapting to them? Or are people perfectly fine with the current, static approach (inbox, folders, sent) that every email client uses today?

Looking for some genuine guidance before we spend time building out this dynamic UI.

I’m currently building out the backend architecture for a new email client. Our core focus right now is implementing a memory system that learns how you work tracking what you ignore, what you prioritize, and your actual context, rather than just acting as a dumb pipe for messages.

While mapping this out, we had a thought that could either be a massive differentiator or a complete UX disaster: what if the entire frontend application reshapes itself based on what the backend learns?

Basically, moving away from the static "Inbox/Folders" grid everyone has used for two decades. If the system learns you use email primarily for sales, the UI physically morphs into a Kanban board. If you're an engineer, it structures itself like an issue tracker.

It sounds like a great engineering challenge, but I need a reality check before we commit sprints to building this dynamic UI layer.

Will anyone actually pay a premium for an app that constantly adapts its shape to fit them? Or do people fundamentally prefer the predictable, boring rigidity of a standard inbox?

I'm trying to figure out if this is a genuine pain point worth solving or if I'm just over engineering a cool toy.

Would love some honest feedback from anyone here.

Hey guys,

We are currently implementing the backend architecture for our email client. The core focus right now is a system that actively learns from each individual user's behavior and adapts its logic accordingly—learning what you ignore, what you prioritize, and how you work.

While building this out, we had a thought: what if the whole application changes its structure and shape with it as well? Meaning, as it learns about you, the actual UI dynamically morphs to fit your specific workflow (e.g., turning into a Kanban board if you do sales, or an issue-tracker view if you are a dev).

What do you guys think? It sure sounds cool in theory, but will anyone actually pay for an application like this just because it is adapting to them? Or are people perfectly fine with the current, static approach (inbox, folders, sent) that every email client uses today? Looking for some genuine guidance before we spend time building out this dynamic UI.