#theresanappforthatideageneration

[antonyad1]

There’s An App For That final wireframes

Here is the final (so far) concept of the app we are working on. 

Once logged in, the user will be able to add people to their account by searching for those nearby, finding them in their contacts or adding them by username. By completing or skipping this step, the user will see their account page and the people they have added as friends. 

Each user of the app is supposed to take a picture of themselves with each drink they have. When the photo is taken, a window will appear with additional information, asking the user to select the drink they are drinking (in case a mistake was made while scanning the photo) and to indicate who got that drink. The user can then post the photo to their story. Now when the user opens their story, a small icon will appear in the top left corner with a photo of their account, on the right with the time the photo was published, the name of the person who bought them the drink, and the price of the drink. 

Since our brief says that people should be notified about their purchases in the morning, the app will calculate the sum owed and show it on the home page below people's accounts. That way, if someone owes me money, it will say under their profile icon that they owe me money. It will also add a red circle around their profile photo to indicate that. The same when I owe them money. This feature will solve the problem of having too many windows, as one page will tell you who owes how much money to whom. We also thought that when a transaction is completed, users will be able to select a box that says "completed" and the circle around that person's account will change colour to normal. 

[antonyad1]

There’s An App For That Workshop and Tutorial with Justin

This tutorial really pushed us forward. It helped us realise that we don't need to think about every little detail and every user, as it's impossible to please everyone. I also think in our group we went into too much detail and it felt like we were trying to create a real app in 3 weeks, which is hardly possible. 

So, during our tutorial, we all agreed on the idea of creating a social platform where people would take pictures of themselves with drinks, and the app, based on the person's location and scanning the picture, would be able to determine which drink the person is holding and how much it costs. At the time, we didn't yet know how the app would run and how it would tell users how much money is owed to whom. Yes, it's good for remembering how many drinks you had, but it still doesn't tell you how much money is owed to certain people. So we had to solve new problems. 

[antonyad1]

There’s An App For That Workshop 

After discussing how each of us sees our app, we thought about how we could simplify our existing apps and how we could remove the information that needs to be entered, as it is more difficult and time-consuming for someone who is not completely sober to do so. So we decided that we could help the user with this by asking them questions and offering some options so that they could just tick the boxes and forget about it. 

However, it still felt like we were copying other apps and making things too complicated for both ourselves and users. Our app had too many pages and too many features that we had to develop and think about. We tried to figure out how to make it more fun to use, because if the app looks like a boring calculator, people our age won't want to download and use it. 

[antonyad1]

There’s An App For That Idea Generation 

After examining all the apps mentioned below, I made a list of things that I think should be featured in our app, as well as a few sketches of possible layouts. I tried to make it as simple and easy to use as possible for those who are in a hurry or a little tipsy.

[antonyad1]

I found a list of the most popular apps for splitting bills to see what features they have and how they work, to find out what is already on the market and who we are competing with. I also wanted to get a better understanding of how a similar app to ours might work.

So I made screen recordings of each app I was reviewing so that I could go back to these recordings if necessary to see what the user sees when they first open the app: what is displayed on the loading screen, how the login process goes, whether or not there is a tutorial on how to use the app. I also wrote down all the advantages and disadvantages of these apps to use for the development of our project. I thought this might help us solve some of the problems we might encounter when developing our app.