Fluid Viewports vs Fixed Screens in Native Web Apps
Quick Jump / Table of Contents
When designing an experience we must consider the rendering capabilities of the devices and platforms we run on. OakFrame is not only run in our own environments but powering millions of capable experiences. By leveraging the full browser rendering system and offering full control over how that browser renders frames, we are able to take advantage of this rich feature set for every interaction that takes place. So let's find the best ways to deliver optimal views based on hardware capabilities and interface requirements. We will focus mostly on variable viewports to highlight some best practices when designing applications.
Firstly, the humble Web App
We use open source software, as described in our documentation, to build and distribute our software across many platforms. Due to the nature of our interactive systems our infrastructure is really nothing more than a simple web shell running our web services in a sandbox environment. The benefits of using such a system include the ability to scale and support new devices,or devices that may not fit into our expected models.
We consider that process to be the "Native Web App".
Websites are ubiquitous in 2019, with Google's projections from many years back beginning to harken in. Many web projects today have already grown into web apps themselves. In some cases, these web applications started as native client applications and then converted into to web apps, due to increased simplicity and availability of resources. Native web apps offer increased efficiency in development and deployments.
Is it important to use responsive design for my website?
Yes, it definitely is. Responsive website design requires you to be consistent across all of your platforms.