_edited.png){kind=logo}
After presenting our progress in class last week, we decided to change the app name again - hopefully for the last time ;)
We decided to go for a short name that represents fun, naughtiness, and at the same time quick and easy - “WINK” This is also being used as the name of the “I think of you” feature that from now on will be “wink netta”. We felt that in this name there is something daring & audacious, and appropriate to the essence of our app.
This week we have been constantly improving our screens according to the insights from the last usability tests. We changed the Pin by location and the schedule screens according to the notes of the GUI girls and decided to design it in full screen and not in Popup like we designed last time.
In addition, based on an insight from the users' review, we decided to add a "send now" button, because there is a possibility that the user will want to send the gesture immediately and not schedule it.
Before testing our screens one more time, we designed all the flows of our app and added interactions in Figma. We wanted to start doing user testing on a prototype to convey the sense of a real application for the users and we didn’t want to show them the screens without interactions. In addition, we wanted to clarify to the user the meaning of and the values of our application by giving them the opportunity to experiment our interactions for our features.
Also, this week we started researching and focusing more about our brand’s colors and started designing our logo.
Finally, we conducted 5 user tests. The most common feedbacks were:
The user wants to choose the indicator s/he sends.
Sending options should be arranged in order of convenience to the most complex one - sending a gesture immediately, by time, by location.
The user did not understand how the gestures were displayed - pending Vs. Past interaction.
Option to add a ‘love note’ that contains more characters.
The user did not recognize the Wink button.
When we told the user to delete a schduled gesture he did not know how. We should make it more clear and change the deleting button.
When we told the user to enter the history he clicked on the hamburger bar and did not recognize that he should swipe the "send a note" frame left in order to see it.
In coding, we made very good progress this week.
We solved last week's problem and made good progress this week. We managed to fulfill all our goals for this week and even more.
Now we have an app that can upload pictures from the phone to firestore storage and get the download link to it. Then open a new Image object in the fire store RealtimeDatabase. This object has the link to the binary image file we got earlier and other metadata. Finally, the app can present all the Images that are in the RealtimeDB as a “history page”.
We have a lot of work still to do. It’s very tempting to start working on the User side and make a pretty app. We must stay strong knowing that creating a strong reliable backend will benefit us in a few weeks.
