Not every new feature needs its own screen.

It's something worth thinking about when a digital product starts growing.

A new feature gets introduced, so a new page is created.

Then another feature arrives. Another page. Another menu item.

Eventually, the navigation starts reflecting everything the product has accumulated rather than how people actually use it.

And that's where things can become unnecessarily complicated.

When you're designing or improving an existing product, adding functionality isn't just about finding space for another interface.

It's about understanding how that functionality fits into the workflows people already have.

Imagine an invoicing platform introducing automated payment reminders.

You could create an entirely separate section for managing them.

Or you could integrate that functionality directly into the invoice workflow, where users already have the relevant context.

Both approaches can make sense.

If the feature involves complex configurations, reporting, or needs to be managed independently, a dedicated section might be justified.

But if it's something people naturally need while completing another task, moving them to a separate screen could introduce unnecessary steps.

I think this is particularly important with established products.

Every new feature affects more than the area where it appears.

It can change navigation, information hierarchy, existing user habits, and the overall complexity of the experience.

And the more a product grows, the more important those decisions become.

Sometimes introducing a new capability means creating an entirely new experience.

Other times, the stronger solution is making that capability feel like it has always belonged there.

The invoice reminders example makes it clear, the feature stays where people already are. How do you decide when something is complex enough to deserve its own section?

Looking for feedback on my SaaS startup — Publune 🚀

I'm building Publune, an AI-powered platform designed to simplify Instagram content creation and management.

The idea is to bring everything into one workflow:

Upload and analyse photos/videos using AI.

Generate captions and hashtags.

Edit content in one studio.

Schedule and manage Instagram posts.

Organise content through a calendar and dashboard.

I'm currently developing the MVP and would love honest feedback from product designers, developers, marketers, and startup founders.

What features would you find most useful? What's missing, and what would you improve?

I'd really appreciate your thoughts!

Brand voice would be my first add. Captions that sound the same for every account get ignored fast so letting users save a few of their own posts as a style guide helps a lot. I would also check the Instagram Graph API rules for publishing early because they shape the whole...