Is this a map app that people will hold the device in both hands to use? Will the device be on a wall, or will people use it to watch shows while laying down? Any context must be supported by the UI you choose, such as whether it is a one-hand friendly UI, or how many components and possible distractions you allow into the screen space. Consider if users would prefer a portrait or landscape view, or even where they will be using your app. The vital thing is to anticipate correctly the way users will want to use your app, and focus your design efforts on that primary use. Users evidently have different expectations for their phones and tablets, and that must inform our design and UI decisions. However, the most common uses for tablets are currently games and video content, as well as social networks. Phones are our day to day connectivity devices, and studies show we use them primarily to access our social networks, text messages, games, and on the go music. Below we will walk through each area, contrasting for phone and tablet UI approaches. These differences are all UI related, and deal with the context, adaptability, interactivity, and organization of your app at each size. When developing for phone and tablet, there are some important differences to keep in mind to ensure a great experience for your users. So, should tablets share your mobile layout? The answer is usually 'mostly'. This is evident by the fact that they are designated as a separate device category for apps and often require separate app development, while tablet views are often treated as the largest phone size. Tablets are currently in a transient state, sometimes grouped with phones, other times allowed to eat at the desktop table, and the rest of the time considered something else entirely. For the most part, users content themselves to using what functionality is available for the tablet, and developers and designers are already overwhelmed by perfecting mobile and let that work for tablet too. But it turns out that there is still no definitive answer as to what tablets are. Should a tablet follow phone design, desktop design, or should it be its own separate size designation? There is a growing case to say that we have been looking at tablets wrong this whole time. It might seem counter-intuitive to distinguish the phone from tablet development, after all, once you've designed for an iPhone 6+, where, really, is the difference in modifying that for a small tablet? Because both devices are handheld, use downloaded apps, and are operated by touch, there is a temptation to treat tablets as simply the largest phone size, which for many reasons we will discuss later, is the wrong way to approach tablet app development.

Both are considered 'mobile' devices, but from a UI perspective, they can be quite different.

Ui browser vs