[UX] Considerations and questions of the Responsive web/UI design
1. Example of Responsive Web(UI)
Here is an example for understanding Responsive Web(UI).
(source: venque.co.kr)
Before I state this topic. I would like to say where this definition comes from. This definition is not so new for me. Obviously this kind of concept was researched by Jacob Nielson, father of Usability few years ago. The related concepts are 'Progressive disclosure', 'Responsive disclosure'. I think 'Responsive Web(UI) inherits this kind of philosophy.
Anyway, in this article, I would like to tell you why we should consider Responsive Web(UI) when we plan a web service and UX.
2. Questions and Answers
Question 1: Do you have thought about what is the most important thing to develop Responsive Web(UI), by the way?
Answer 1: I think that is the consistency of the user experience from mobile site to desktop site. You can think what happen to you if you can't experience the service in a mobile site like desktop site.
Of course, I don't mean all of UI controls should be designed alike. That should be designed differently for each site because each site should consider each characteristic of the device. For example, mobile site should consider haptic interaction but desktop site is not necessary about that. I don't want to talk about the detail design guideline for Responsive Web(UI) in this topic, no matter what.
Question 2: Why do we consider that even if it is hard to develop that and it takes too much time to develop?
Answer 1: That's true. It takes more time to develop that site, and it means you need more budget, but if you think about the development of mobile app or mobile web. That will save your money for sure even though it costs more at the first step. In addition, web technologies like HTML5 is getting more fabulous, so it will easier to develop and you won't need so much time to develop as much as now.
Question 3: Do you mean this Responsive Web(UI) is omnipotent for any web services?
Answer 3: I don't think so. That's a way to develop both of the sites, mobile and desktop sites. Normally, many company just develop each site without consideration of Responsive Web(UI).
Question 4: If so, why should we consider that?
Answer 4: I want to answer this question for an economic point. You can make it of each but you should operate and support all the sites. What does this mean? You need to spend more money for them while developing and maintaining. Moreover, If you can't support a new device with a present site in the future, what will you do? Will you make another site for that again? That's why I said this is more economic when you consider supporting many devices at the same time.
Question 5: When do we decide this approach, by the way?
Answer 5: If you have a plan to continue your service and support all kinds of devices, do consider this. If you don't have enough time and money to maintain the system and the site but you want to launch the service for many devices, do this. It's up to your business strategy. Think about what your business strategy is before you think if you should consider this or not. That's more important.
Question 6: What is the most important thing if I decide to develop a Responsive Web(UI)?
Answer 6: As I said above, consistency of the service is the most important thing. I have seen many services that I can't check out on a mobile site, so I should go to desktop site with my laptop again. That really sucks, and I didn't understand what they developed the service. If you think you never make it for all your sites, just give it up and make each site separately.
3. Summary
-The service consistency is the most important thing for this approach.
-This is more economic than developing the site of each if you support many devices, so think about what you really want to do with your business strategy.
블로그 관리자가 댓글을 삭제했습니다.
답글삭제