One of the biggest demands by clients that we face is providing websites and applications for mobile devices. It’s no big news that web design is in a state of flux with the introduction of a wave of mobile devices, each with varying screen sizes and functionality, which raise a whole range of questions about web design best practice. Within the mobile app market, there is much debate over which is the better of two contrasting systems to deliver content to mobile devices - native applications, which can be downloaded from app stores and are installable software, and web apps - effectively websites that respond to being viewed on mobile devices.
Many argue that native apps offer better user experience; they are typically run much faster and utilise device functionality to perform sophisticated tasks, making them feature rich - plus, they don’t always require an internet connect to work. There are however drawbacks - they consume device resources, such as battery life; and require regular updates to maintain security and update their functionality. Not to mention that the issue that comes with market penetration. For example, Twitter’s mobile app might appear exactly the same on both Android and iPhone - but they will be built from different technologies - Java and xCode respectively. This presents large overheads when it comes to maintaining multi-platform apps for one service.
Mobile web apps
- Wired magazine - Native apps vs mobile web
- The guardian’s smart accessibility is packed full of useful information about mobile accessibly.
- The W3C - WAI mobile accessibility
- IBM - how do native apps measure up to accessibility
If you would like to chat about how S8080 could help improve mobile website design and user experience, call 01792 485566 and ask for Chris or Matt, or email, email@example.com.