diff --git a/book-pop.html b/book-pop.html index 33c8537..8531d74 100644 --- a/book-pop.html +++ b/book-pop.html @@ -94,30 +94,36 @@
My Role: UI / UX Designer
+Tools: Miro, Adobe XD
+We checked different apps related to books and events, to understand what was already available on the market.
-We liked how the books were shown as a list and we analysed the information displayed for books and events.
- ++ We checked different apps related to books and events, to + understand what was already available on the market. We + liked how the books were shown as a list and we analysed the + information displayed for books and events. +
+ We decided the app should use + bright colours and round shapes and have + some nice illustrations inside it, so + parents and children would use the app together to look at + the books available at the different events. +
- I created some wireframes and a rough prototype with - those. -
-Then I conducted a usability test.
-- Users did not understand the section had both the - liked recipes and the user ones. -
-- → solution: changing the - label in "My Recipes and Favourites" -
-- Users did not understand the section had both the - liked recipes and the user ones. -
-- → solution: changing the - label in "My Recipes and Favourites" -
-- Users did not understand the section had both the - liked recipes and the user ones. -
-- → solution: changing the - label in "My Recipes and Favourites" -
-+ We thought the app main will have a system for joining and + creating events and possibly a section were the child can + check out all the books available and like some. This + section would have a character to guide the child through + the app. +
- I created the style guide and the high-fidelity screens. -
-- I ran a A/B test to clear some doubts. -
-- 60% of the participants liked more Choice 1. From this test - I also understood participants preferred to have less - categories, so I decreased the categories to 5. + From our wireframes emerged + two different approaches for showing the events, one using a map and the other using a list. The map would + allow the user to immediately spot events nearby, however + the list allows an easy comparison between the events, + viewing immediately details such as time and target age. We + decided it could be useful to have both of them and the user + could simply change from one to the other.
- I created the responsive screens and - finished working on the - high-fidelity screens. -
-+ We decided the home screen would show the books available + at nearby future events. It seemed important to us to show + some books in the main screen since books are the topic of + the app. We also noticed similar apps were doing the same, + which encouraged us to move towards this direction. +
+We found challenging creating the event screen, in particular showing all the info in a clean way and also keeping the "Join in" button always on screen and recognizable from the background. + One trick that aided us was making the participants and books section horizontally scrollable.
+- Since we did not have much time, we did not create the icons and illustrations ourselves but used some from Icons 4 Design, Noun Project and Ouch!. + +
+ Since we did not have much time, we did not create the icons and + illustrations ourselves but used some from + Icons 4 Design, Noun Project and + Ouch!.
- “I usually cook quickly something easy” --
- Solution:
- A collection of recipes that can be made quickly with
- easy-to-find ingredients
-
- “I choose what to eat according to what I feel like eating - at the moment” --
- Solution:
- Taste filters to get quickly to what you want
-
+ “I want to find book swapping events so I can swap / borrow / + donate books” ++
+ Solution:
+ The app allows users to find upcoming events. The user will
+ get asked when joining if they want to swap, donate or borrow
+ books.
+
- “I have my own family recipes or use Google to search for - something” + “I want to create events so I can invite my friends and the + neighbours”
Solution:
- Add your recipes to the app and have everything in one
- place.
+ The user can create events and invite friends.
- “Sometimes I want to cook something from a certain country, - or a specific diet type. I pay attention to eat healthy.” + “I want to be able to see who will come to the event and + what books I will find.”
Solution:
- The app menu has different sections for each need: World
- cuisine, Diet and Balance menus.
+ The event page has a list with the participants and with the
+ books that they will bring.
+ After the creative jam, we made some further edits to the app. My teammate made some testing: a survey and some usability testing. That way we wanted to see if people were actually interested in the app and what was working well. + Some of the big changes we made were: +
+ We got in touch with some volunteer developers and decided to change the project into a web
+ app, since for them it would have been easier to make a web app rather than a native one.
+ The major changes that I have applied as I updated the screens are the addition of the footer
+ to all the pages and the disappearance of the tab bar. I have also
+ reduced the amount of features so we could launch with a Minimum
+ Viable Product. We established it was essential to be able to create and join the events, but the feature of adding the books you would bring to the event was not so important for the moment.
+
+ Unfortunately this project wasn't eventually launched as a web app. + However we learned a lot from it.
++ To sum up, the project was a great learning experience and we + managed to improve our understanding on collaborating with other + people and of product development. Even though we did not launch it, + we think when it will be the right time we might get back into it. +