Engineering·1 min read
Why We Chose Flutter Web for the App Hub
The tradeoffs behind using Flutter Web for interactive catalog experiences while keeping web marketing separate.
The App Hub has two jobs: it needs to present products clearly, and it needs to stay flexible as the catalog grows. That makes the frontend choice important.
Where Flutter Web fits
Flutter Web works well when we want:
- highly controlled layouts,
- app-like interaction patterns,
- shared UI logic across platforms.
Where Next.js still leads
For marketing pages, Next.js is still the better fit because it gives us:
- strong SEO defaults,
- clean route structure,
- simpler content publishing for blogs and docs.
The split that works
We treat the public marketing site and the product catalog as related, but separate surfaces. Marketing drives discovery. The App Hub drives product exploration.
That separation keeps each surface optimized for its job instead of forcing one stack to solve every problem.