Users' wishes 'Please don't make me confused.'

Users' wishes 'Please don't make me confused.'

 One of the greatest challenges in designing and developing a web application is making it intuitive. But what does this really mean when we say that an application is intuitive? Making an application that seems familiar and is easy to use is part of it. Knowing what is required of you at every step of the way and how to achieve your goal is another. Being able to know that a button is a button and knowing what a button will do before you click on it are yet other qualities. Essentially, what it means is that a user is able to intuit his/her way around the application without having to think too much about it.

 The reason why this is so challenging is that it requires all of the elements we have considered previously to come together in the right balance. It is just as much a factor of design, color, layout, position and shape as it is behavior, responsiveness, timely feedback. The tendency is that when there are so many elements involved that need to work perfectly in harmony, the interface becomes overloaded and bland by giving equal importance to each of the elements. As we saw with limiting our color palette to achieve more impact with our application's visual identity, the same reasoning can be applied to be able to achieve a user interface which is intuitive.

 The hardest part about creating something is being able to throw it away if it is not working. Creating a satisfying user experience through an intuitive interface will require that the interface become complex whilst remaining uncomplicated. It will require the ordering, by priority, of each component and it will also require the removal of those parts which are not essentially necessary. Taking elements away or merging them in order to simplify an interface will make the remaining choices clearer and more relevant.

Users' wishes 'Please don't give me extra work.'

 When creating a user experience that is elegant and enjoyable, along with an intuitive interface - one that doesn't require the user to think too much, we also need to try and create an experience that doesn't require too much work to complete a task. Like the intuitive interface, this is a difficult one to master as it is also the culmination of a number of separate elements. Navigational structure is probably the most significant, specifically the size, position, shape and color of the navigational elements. Minor changes like putting spaces in between tabs can increase usage significantly.

 Thinking of desired user activities within the application in terms of paths or flows can help in the design process towards creating user experiences that are satisfying and effortless. Activities like sending a message, requesting a friend, starting a course, and acting on recent activity are examples of some relatively short and standard user experiences within iKnow!. Most of these activities are fairly familiar to most users and, as such, it is hard to go wrong with these. Designing the user experience of building a list was a little more tricky.

 The List Builder is a place where the user can spend quite a bit of time making content for themselves or other iKnow! users. When designing the user experience for this List Builder we had this in mind and tried to make the experience as simple as possible. We used a system of layered contextual interactions that were loosely interdependent. The first action of searching for an item and adding that item to your list takes place on the first layer. This allows a user to quickly build a list filled with default content (like sentences and images) on this layer without digging in deeper. In this way a list can be quickly filled with rich content for the user who is not specifically interested in managing their items further. The second layer, that allows the user to create and attach sentences to an item, occurs in the lightbox modal window, and, as such, can be an optional step in the list building flow.

 Well I guess that is about it for this series. For those of you who made it this far I say thank you and お疲れさまです. I hope it wasn't as hard for you to read as it was for me to write! And if you are interested in improving your English skills, or if you would like to watch a web application in constant review, then take a look at iKnow! and learn with us.

人気記事トップ10

人気記事ランキングをもっと見る

企画広告も役立つ情報バッチリ! Sponsored

ClickHouse Cloudが実現した広告運用SaaS「ATOM」のデータ基盤革新、パフォーマンスを向上しながら、運用負荷とコストを削減 11月11日 6:20 AIで開発が加速する時代、品質保証はどう変わる? Tricentisが示すAIエージェント活用の実像 11月9日 6:45 悪用までの猶予が「1分」に迫るフロンティアAI時代に開発と本番を貫く脆弱性管理が必要 10月29日 8:30 欧州CRA対応とSBOM運用。AI生成コードのOSS混入問題の対策とは ――スニペット単位で検出する「FossID」「Insignary Clarity」によるSBOM運用 9月16日 6:40 PostgreSQLからTiDBへ、稼働中SaaSで進める段階的DB移行の実践と再設計への展望 9月7日 6:30 機能安全開発におけるGoogleTestの活用を支援!「Parasoft C/C++test CT」で実現する効率化&AI連携 4月14日 6:30 【CNDW2025】Grafanaが明かす「オブザーバビリティの哲学」ー最小限の労力で実用的なインサイトを得るには 1月23日 6:30 【CNDW2025】プロダクト急増に備える基盤刷新 ーウェルスナビがECSからEKSへの移行で得た知見とは 1月15日 6:30 【CNDW2025】250環境を5人で運用、構築時間は30分に ーKINTOテクノロジーズが語るインフラ基盤組織の作り方 2025年12月18日 6:30 新たな自動化で熱視線! AIエージェントの「推論能力」を支える2つのコンポーネントとは? 2025年11月28日 6:30