Webflow, Astro, Framer or Expo: how I choose
How I choose a platform around what needs building, who will maintain it and what changes after launch.
It's easy to put Webflow, Astro, Framer and Expo in the same comparison, but I'd separate what you're trying to build first. Webflow, Astro and Framer can each play a part in a website. Expo is mainly for applications across native devices and the web.
Then I'd look at who's going to own it. Can they maintain, extend and measure what we build? That's the question I find useful when choosing between them.
Start with the team, not the tool
Choose the closest answer. This narrows the conversation, but the content model, integrations and long-term owner still matter.
Likely starting point
Webflow
A marketing team needs visual control, a capable CMS and a fast route from design to launch.
Check before committing
It becomes less comfortable when the product needs deep application state or native mobile behaviour.
The next option from these answers is Framer. A hybrid can be sensible when the marketing site and product have different owners.
The quick comparison
| Platform | Choose it when | Be cautious when | Natural owner |
|---|---|---|---|
| Webflow | A marketing team needs visual control, structured content and fast page iteration. | The project depends on deep application state or complex product logic. | Marketing, design or website team |
| Astro | The site is content-led, performance matters and the team wants control of a codebase. | Nontechnical editors need to reshape page layouts visually every day. | Developer with content or marketing input |
| Framer | A design-led marketing site needs to launch quickly with expressive layout and motion. | Content operations, integrations or application logic are likely to become complex. | Designer or small marketing team |
| Expo | The core experience belongs on iOS and Android and benefits from shared product code. | You only need a conventional marketing website or content publication. | Product and engineering team |
Start with what you're building
For a marketing website, the work centres on publishing, campaigns, content and conversion journeys. A product brings state, accounts, permissions and behaviour into the picture. Mobile may need notifications, device APIs and store releases too. Once the main job is clear, the platform choice has something to work from.
You can keep those choices separate. A portal can have a Webflow marketing site, and an Astro publication can link to an Expo product. Different users and owners may need different platforms.
Webflow when marketing needs visual control
Webflow makes sense when marketers and designers need to create pages, work with structured CMS content and see their changes in context. If most of the team's work happens on the website and they change it regularly, that can be a useful fit. You do give up some control over the rendering stack.
I still use Webflow for work that fits it. Where I'd be careful is an application whose first few screens happen to be easy to build there. Once user state, permissions and business logic become central, I'd usually separate the product stack.
Astro when you want a content-led codebase
Astro is designed for content-driven websites and sends very little client-side JavaScript by default. It suits publications, marketing sites and large content libraries where performance, control of components and a maintainable codebase matter.
That's why I use Astro for this website. I can control the routes, structured data, content components and interactive islands such as the planner. In return, I'm mainly managing page structure in code, even when the content comes from a CMS.
Framer for a focused design-led launch
Framer suits a focused marketing site where layout and motion matter and you want to launch quickly. Its current editing tools let permitted collaborators change visible content and CMS pages from the published site.
I'd be more cautious if the brief involved lots of structured content, connected systems or product logic. A quick launch is useful, but I want the platform to fit the work six months later too.
Expo when the product is an app
Expo gives you a React Native route to iOS, Android and web applications. I'd consider it when the mobile experience is the product, rather than another way to read the website.
I use Expo for mobile app development because the shared TypeScript and React foundation can support the product across devices. There's still room for platform-specific behaviour where you need it. Store distribution, device testing and mobile releases remain work in their own right.
Five questions I'd ask before choosing
- Who owns the platform after launch? A designer, marketer, developer or product team will each tolerate different workflows.
- What changes every week? Campaign pages, structured articles, application logic and native releases need different operating models.
- Where does the source of truth live? Decide whether content, customer data and product state belong in the platform or in connected systems.
- What is likely to become complex? Content volume, roles, localisation, integrations and approval can reveal the future constraint.
- What would make leaving expensive? Understand which designs, data and components can be reused if the business outgrows the platform.
When two platforms can be simpler
One system sounds simpler until the marketing site and customer product need different release schedules, permissions or technical choices. Keeping those boundaries clear can mean fewer compromises.
That split makes sense where there's a clear product or ownership boundary. Once it's there, navigation, analytics, identity and brand still need to work together across both parts.
Official references
- Webflow: visual CMS and content management
- Astro: content-driven, server-first architecture
- Framer: web, CMS and design pages
- Framer: on-page editing
- Expo: building universal React Native applications
Frequently asked questions
How do I choose between Webflow, Astro, Framer and Expo?
Start with what you're building and who will own it. Compare content editing, interactions, integrations and release channels. Prototype the hardest requirement before picking a platform for its templates.
Is Expo an alternative to a marketing website builder?
Expo is a framework and toolset for building applications. It can support web and mobile products. A marketing site with regular content edits needs different things from a signed-in app, so decide how to deliver each separately.
Can one business use more than one platform?
Yes. The marketing site and application can use different tools if their needs differ. Agree who owns shared content, navigation, authentication, analytics and design tokens so the split doesn't create extra operating work.
.jpg)
