Frontity Docs
  • » Welcome to Frontity
  • 🚀Getting started
    • Quick start guide
  • 📃About Frontity
    • Frontity features
    • Browser support
    • Get involved
  • 📚Core Concepts
    • 1. Project
    • 2. Settings
    • 3. Packages
    • 4. Roots
    • 5. State
    • 6. Actions
    • 7. Libraries
    • 8. Namespaces
    • 9. Styles
  • 🏗️Architecture
    • Decoupled Mode
    • Embedded Mode
  • 🌎Deployment
    • Deploy Frontity using Vercel
    • Deploy Frontity on Layer0
    • Deploy Frontity on Heroku
  • 🌗Isomorphic React
  • ⚡️ Perfomance
    • Caching
    • Link prefetching
    • Lazy Loading
    • Code Splitting
  • 🔎SEO
  • 📖Guides
    • Setting the URL of the WordPress data source
    • Using Environment Variables in a Frontity project
    • WordPress requirements for Frontity
    • URLs in a Migration from WordPress to Frontity Decoupled Mode
    • Frontity Query Options
    • Redirections with Frontity
    • Understanding a Frontity project
    • Add a new Frontity package or theme to your project
    • How to share your Frontity project
    • Understanding Mars Theme
    • Working with processors
    • How to process page-builder content in Frontity
    • Keep Frontity Updated
    • Troubleshooting
    • JavaScript
    • React
  • 👏Contributing
    • How to contribute?
    • Contributing Guide
Powered by GitBook
On this page

Was this helpful?

  1. About Frontity

Browser support

PreviousFrontity featuresNextGet involved

Last updated 4 years ago

Was this helpful?

The approach adopted by Frontity is as follows:

  • Prioritize the performance and user experience for the large majority of users that run modern browsers.

  • Do this while keeping as much compatibility as possible for the small minority of users that still use older browsers, such as IE11.

"as much compatibility as possible" here means that at the very least the page loads, the content can be viewed and read, and the user can navigate to other parts of the site.

Platform

Support

Full hydration

Browsers without Proxy (like IE11)

No hydration (SSR-only)

We don’t expect feature parity between the SSR-only version and the fully hydrated version. You can think of the SSR-only version as an alternative version of your page, without the enhanced experience provided by React.

If you need to provide the feature parity in IE11, then Frontity is probably not the best option for you.

📃
Browsers with Proxy