Through feedback of the final interface design, it was pointed out that since the function of this interface is neither an app nor a website, in the real design world clients would expect to see a responsive version of this interface.
Jim Boulton talks about the importance of responsive web design when working with design for screen. "Increasingly, the most important screen is our phone, the last screen we look at at night", however content optimised for larger screen experiences often produces disappointing results when viewed on smaller screens or vice versa when design for smaller screens is viewed at larger resolutions. This issue therefore prompted Ethan Marcotte to coin the term 'responsible web design', becoming particularly inspired by responsive architecture whereby buildings react and adapt as people pass through them. He stated that "rather than tailoring disconnected designs to each of an ever-increasing number of web devices, we treat them as facets of the same experience. We can design for optimal viewing experience, but embed standards-based technologies into our designs to make them not only more flexible, but more adaptive to the media that renders them".
In further developments to the final interface, such responsive design would therefore need to be catered for if this user experience were to also eventually be developed into a mobile app, whereby it would possibly get more use in terms of function since mobiles have been researched to be the most important screen in ux design. This research shows how designing a responsive version of my interface does not have to replicate an exact version of the interface on a smaller scale, but elements and standards in it's overall design can be taken and utilised to make the responsive version function better at a smaller resolution whilst staying consistent with the design of other versions.
No comments:
Post a Comment