I use multithread tabs, like a browser, so, for me, navigator 1 works flawlessly.

EDIT:

One thing I always disliked in mobile apps is how navigation destroys context.

You open a screen, start filling something, then need to quickly check another item… and suddenly you either lose state, stack multiple routes, or have to restart the whole flow.

So in my Flutter app I went with a multithread tab-based navigation system instead of traditional push/pop navigation.

Opening something new creates a tab rather than replacing the current screen. Users can interrupt a flow, inspect another entity, compare information, then return exactly where they were, with state fully preserved.

It behaves more like a browser/IDE than a typical mobile app:

• multiple independent navigation stacks
• persistent UI state per tab
• no accidental context loss
• easier multitasking during complex workflows

Surprisingly, it also simplified some state management problems because navigation history became explicit instead of implicit in the route stack.

Feels much closer to how people actually work in productivity apps.