> Intro:
>
> We see all of the time the assumption that parity should be found across native and web platforms. We assume that we’re building the same product regardless of surface, but we don’t consider each platform's strengths and how we should be leveraging them better.

This is: *an attempt to draw a distinction between native and web platforms, considering what they’ve been best at historically.*

### Native apps: For using

* Interactivity: Native apps should emphasize interactivity, where users are actively engaged in performing tasks, manipulating content, or interacting with app functionalities.

* Utility and Productivity: Native apps should be built around specific utilities or productivity goals. Users don’t just consumer content; they create, modify and control it.

* Personalization: Native apps should leverage personalization to make the user’s interaction with the app more tailored an experience to better suit the user’s needs.

* Immediate and Quick

### Web apps: For consuming

* Information and Content Consumption: Websites traditionally have been used for reading, watching or listening to content (news, blogs, youtube, etc.)

* Accessibility: Websites are easier to access — just type in the url — so that makes it ideal for quickly finding information and consuming media.

* Interactivity and Engagement: While websites are often used for consuming content, we’re trending more app-based which is allowing us to blur the lines between native and web platforms and design with more parity in mind (tho the way we interact with native and web apps is still quite different and maybe that is worth discussing more — gesture based, context based interactions depending on the device you’re looking at your content on ?)

* Long Form and Complex

Native v Web (Rough Draft)

On Interaction

On Fluidity

On Flexibility

On Simplicity

On Design