Final feedback

I had some really positive feedback for my app, most people really liked the idea and found the design appropriate and thought that the app was overall pretty easy to follow. Most of the feedback I received was how to develop the app further rather than criticism. People really liked the colour use and thought they were friendly which was a big requirement of the app. They also really liked the images used and found that viewing a lot of images made them hungry and would potentially encourage them to bake. 

A suggestion was to make the yellow squares on the recipe slides smaller and less bulky, people found them too in your face and distracting. My idea was to draw the users sole attention to this area of the slide, however if I was to develop the app further this would be something I would try and alter. Another suggestion was that some of the images are too dark and aren't very homely, I can understand this however the images displayed would be seasonal and as we are in autumn/ winter right now these recipes are fitting. 

Everyone found the logo and branding suitable for the app and thought it would be recognisable if the app was to then come a book or merchandise etc.

Overall I am really pleased with how my app has turned out and Im glad that other people like it too. 

Final Design Stills

=

Final Design

Module Evaluation

Overall I have really enjoyed the module and the fast pace nature of it. I have found that working on short briefs has encouraged me to work quicker as I have had less time to deliberate on ideas, instead I have plunged straight into work. Despite this I have still made all of my design decisions considered. I much prefer working in this way as I haven't got bored at any point or felt like I ave spent too long on one specific project.

The publication brief was slightly disappointing as I was really looking forward to designing for my own idea. Megan's idea was a lot different to mine as hers was a guidebook to a city whereas my idea was a recipe book. This brief was very rushed as it took a long time for Megan to provide me with the content required and when I did receive it, it was very limited. Because of this I had to  do my own research and find things to put in the book, however as I didn't have much time I couldn't find much content which made the book quite short. In my opinion I think it is an acceptable length as the main idea of it is to use it as a guide to a day out in Krakow therefore it doesn't need to be too long. I think there are other elements to the booklet which show I have been considerate and spent a lot of time creating it such as: the collages, the Japanese bind and the paper stock. Despite the few problems I came across,  it did give me some experience as to what it would be like working with a client and the issues that would arise. I tried to look at this in a positive way and use it as a beneficial experience.

As for the second brief I really enjoyed this and found it less stressful, a lot of the time I didn't feel bogged down as if I HAD to do work like with the previous brief, I found this one much more relaxing and fun to do.  Despite the fact I had never done any design for screen previously I think I am now pretty competent at it. I looked at a lot of the apps I use everyday throughout the process to aid me with my design as I needed to know the best/ most popular places to arrange things on a page. A lot of the research I did in the initial stages such as looking at the Apple iOS UX requirements also helped me throughout the process as it informed me the do's and don'ts for designing an app. I was initially worried about how I would come to animate the app once I had designed it however, with a basic animation workshop run at uni and watching youtube videos I managed to do an animation in a very basic which I am proud of. In the future I would like to develop these skills and become better at using Adobe xD as I think it is a very useful programme. When I do more design work in the future I may consider looking at After Effects as I think this would be a useful skill to have.

I have realised that working on a brief I have a specific interest in such as the baking app I created has helped me produce better work as I have more knowledge in that field and it is more appealing to me. I will keep this in mind for future and tailor the work to suit my interests where possible.

SB2 Evaluation

Initially I found this task very daunting as app/ web design is something I have never done before. Despite this I ended up really enjoying it and it is definitely something I want to do again in the future. In terms of the branding for the app I only spent about 1-2 hours doing this as to not waste time, however I really like the logo and colour scheme I managed to produce. I really struggled when it came to merging the illustrations into the app as initially they weren't very consistent with the design and it took me a long time to decide on the style to use. When I got over the hurdles that occurred the design process was very smooth and I got a lot of positive feedback along the way in terms of the design looking sleek and simple. One of the biggest things that I had to bare in mind when designing was to not make it over complicated for the user as I didn't want to put them off baking when the app's main purpose is to encourage them to fit it into their busy schedule. 

Overall the most time consuming thing of the whole process was learning how to use new creative cloud apps such as Xd, as well as features I had never used on things such as photoshop. However, the workshops put on at uni were very useful and helped me make a pretty basic video of the app in motion. I am pleased with how the app has turned out and believe that with more time to develop it further it could be a very useful app, however I am satisfied with the point I am at and think it is a very well developed and well designed app considering the short time scale we have had to create it.

Designing the recipe

To add interest to the page and to keep the user focused on the end goal (making something delicious to eat) I decided to place the recipe information over the top of the image of the thing being made.



I then realised the user would need a button or something so that they could click onto the next step with ease. I added a large yellow button so that it was eye catching and also consistent with the colour scheme. It is also clickable without having to over stretch your thumb but this may not be a problem as the user pay have their phone down on the work bench or on a stand however there is also a feature to use your voice to go onto the next step.





I considered that maybe the image in the background could be confusing therefore I decided to try a yellow block in the background however this was far too simplistic and I thought it would get boring to look at for the user and wouldnt be very inspiring.



I then merged the two ideas together, I think the yellow emphasises the recipe well and draws all the attention to it therefore it is easy to ready and glance at quickly.



I then reduced the opacity of this layer so more of the image underneath could be seen as well as adding a 'step 1' button so that people can click on to the next step. I then realised I needed to show the voice recognition somehow so I decided to use a microphone symbol.



The voice recognition symbol is displayed in the top menu bar next to the logo so that it is easy to see, the voice recognition becomes active as soon as the recipe is started if this option has been selected. To turn it on or off the user simply taps the icon and this reveals a simple drop down menu featuring a on/off switch.


Here is the drop down menu, it is very simple and easy to adjust to make it quick and easy for the user.

App Icon

I decided to design an app icon of what it would look like on someones phone screen.


The first icon I designed was this, I decided to use a white background to keep things simple as a lot of the apple apps do this. I used the yellow logo so that it stood out from the rest however I find this too flat.



I tried making it look more exciting by adding a grey fading background to tie in with the colour scheme however I find this too dark.



I then reverted back to the white background but incorporated the grey by overlapping it on the yellow logo underneath.


After looking at the other app icons out there I realised that they rarely contain text as the name is already displayed underneath the icon. I decided to remove the name and simply display the logo for whisk. I think this makes it more easily recognisable and will be using this design.

How do people hold/ use their phone

This pie chart shows the different ways people use their phones. The phone and speaker symbols account for when the phone is either held to users ear or in their pocket. The other results show the thee most common ways to hold your phone and how popular they are. One handed got a results of 49%, cradled was 36% and two handed was a low 15% therefore the most popular way to hold a phone means using it with just one hand therefore my design needs to take this into consideration and be usable in this way. The important buttons should be at the bottom of the page where possible. However with the new iPhone feature that lets you double tap to access the top of the screen there is no area that is out of bounds.

Sliders - Human Interface Guidelines

Sliders

A slider is a horizontal track with a control called a thumb, which you can slide with your finger to move between a minimum and maximum value, such as screen brightness level or position during media playback. As a slider’s value changes, the portion of track between the minimum value and the thumb fills with color. A slider can optionally display left and right icons that illustrate the meaning of the minimum and maximum values.

Customize a slider’s appearance if it adds value. A slider’s appearance, including track color, thumb image, and left and right icons, can be adjusted to blend with your app’s design and to communicate intent. A slider that adjusts image size, for example, could show a small image icon on the left and a large image icon on the right.

Alerts - Human interface guidelines

Generally, use two-button alerts. Two-button alerts provide an easy choice between two alternatives. Single-button alerts inform, but give no control over the situation. Alerts with three or more buttons create complexity and can require scrolling, which is a bad user experience. If you find that you need more than two choices, consider using an action sheet instead.

Give alert buttons succinct, logical titles. The best button titles consist of one or two words that describe the result of selecting the button. As with all button titles, use title-style capitalization and no ending punctuation. To the extent possible, use verbs and verb phrases that relate directly to the alert title and message—for example, View All, Reply, or Ignore. Use OK for simple acceptance. Avoid using Yes and No.

Place buttons where people expect them. In general, buttons people are most likely to tap should be on the right. Cancel buttons should always be on the left.

Label cancellation buttons appropriately. A button that cancels an alert’s action should always be labeled Cancel.

Identify destructive buttons. If an alert button results in a destructive action, such as deleting content, set the button’s style to Destructive so that it gets appropriate formatting by the system. Additionally, provide a Cancel button so people can safely opt out of the destructive action. Make the Cancel button bold by marking it as the default button.

Allow people to cancel alerts by exiting to the Home screen. Accessing the Home screen while an alert is visible exits the app. It should also produce the same effect as tapping the Cancel button—that is, the alert is dismissed without performing any action. If your alert doesn’t have a Cancel button, consider implementing a cancel action in your code that runs when someone exits your app.

Tab bar icons

To make my icons easily recognisable I used existing ones that I found online, I didn't want to create my own as I though this would make the app difficult/ confusing to use. I also located it in a familiar place which is also easy to click on as the user doesn't have to over stretch their thumb when holding their phone in one hand.




I then made a bit of an alteration to my tab bar, I decided that the 'like' (heart) wasn't relevant and I changed it for a timer. The timer will be set automatically when the person puts their cake in the oven to avoid any over baking, however there would need to be an option to turn this off if the timer wasn't required or if the cake was baked before the timer was up. I followed the apple guidelines and used a timer which was a full circle rather than the outline, this makes it easier to see. The yellow line displayed below the home button indicates that this pages is the one that is selected/ the user is currently on. I think this makes it easier to navigate through the app.

Tab Bars and Toolbars- Human interface guidelines

Tab Bars

A tab bar appears at the bottom of an app screen and provides the ability to quickly switch between different sections of an app. Tab bars are translucent, may have a background tint, maintain the same height in all screen orientations, and are hidden when a keyboard is displayed. A tab bar may contain any number of tabs, but the number of visible tabs varies based on the device size and orientation. If some tabs can’t be displayed due to limited horizontal space, the final visible tab becomes a More tab, which reveals the additional tabs in a list on a separate screen.

It’s important to understand the difference between a tab bar and a toolbar, because both types of bars appear at the bottom of an app screen. A tab bar lets the user switch quickly between different sections of an app, such as the Alarm, Stopwatch, and Timer tabs in the Clock app. A toolbar contains buttons for performing actions related to the current context, like creating an item, deleting an item, adding an annotation, or taking a photo. See Toolbars. Tab bars and toolbars never appear together in the same view.

Toolbars

A toolbar appears at the bottom of an app screen and contains buttons for performing actions relevant to the current view or content within it. Toolbars are translucent, may have a background tint, and often hide when people are unlikely to need them. For example, in Safari, the toolbar hides when you begin scrolling the page since you are likely reading. You can show it again by tapping the bottom of the screen. Toolbars are also hidden when a keyboard is onscreen.

For my app I will be using a tab bar, the requirements for this are:

In general, use a tab bar to organize information at the app level. A tab bar is a good way to flatten your information hierarchy and provide access to several peer information categories or modes at once.

Use a tab bar strictly for navigation. Tab bar buttons should not be used to perform actions. If you need to provide controls that act on elements in the current view, use a toolbar instead. 

Avoid having too many tabs. Each additional tab reduces the tappable area for selecting a tab and increases the complexity of your app, making it harder to locate information. Although a More tab can display extra tabs, this requires additional taps and is a poor use of space. Include essential tabs only, and use the minimum tabs necessary for your information hierarchy. Too few tabs can be a problem too, as it can make your interface appear disconnected. In general, use between three and five tabs on iPhone. A few more are acceptable on iPad.

Don’t remove or disable a tab when its function is unavailable. If tabs are available in some cases but not in others, your app’s interface becomes unstable and unpredictable. Ensure that all tabs are always enabled, and explain why a tab’s content is unavailable. For example, if there are no songs on an iOS device, the My Music tab in the Music app explains how to download songs.

Always switch contexts in the attached view. To keep your interface predictable, selecting a tab should always affect the view that’s directly attached to the tab bar, not another view elsewhere on screen. For example, selecting a tab on the left side of a split view shouldn’t cause the right side of the split view to suddenly change. Selecting a tab in a popover shouldn’t cause the view behind the popup to change.

Make sure tab bar icons are visually consistent and balanced. The system offers a range of predefined icons for common use cases. You can also create your own icons. 

Custom Icons - Human interface guidelines

https://developer.apple.com/ios/human-interface-guidelines/icons-and-images/custom-icons/

Custom Icons

If your app includes tasks or modes that can’t be represented by a system icon, or if the system icons don’t match your app’s style, you can create your own icons.

Create recognizable, highly-simplified designs. 

Too many details can make an icon confusing or unreadable, the best icons use familiar visual metaphors that are directly related to the actions they initiate or content they reveal.

Design icons as glyphs. A glyph, also known as a template image, is a monochromatic image with transparency, anti-aliasing, and no drop shadow that uses a mask to define its shape. Glyphs automatically receive the appropriate appearance—including coloring, highlighting, and vibrancy—based on the context and user interactions. A variety of standard interface elements support glyphs, including navigation bars, tab bars, toolbars, and Home screen quick actions.

Prepare glyphs with a scale factor of @2x and save them as PDFs. Because PDF is a vector format that allows for high-resolution scaling, it's typically sufficient to provide a single @2x version in your app and allow it to scale for other resolutions.

Keep your icons consistent. Whether you use only custom icons or mix custom and system icons, all icons in your app should be the same in terms of level of detail, optical weight, stroke weight, position, and perspective.

Make sure icons are legible. In general, solid icons tend to be clearer than outlined icons. If an icon must includes lines, coordinate the weight with other icons and your app's typography.

Use color to communicate selected and deselected states. Avoid toggling between two different icon designs, like a solid version and an outlined version.

Avoid including text in an icon. If you need text, display a label beneath the icon and adjust its placement accordingly.

Don’t use replicas of Apple hardware products. Apple products are copyrighted and can’t be reproduced in your icons or images. In general, avoid displaying replicas of devices because hardware designs tend to change frequently and can make your icon look dated.

Provide alternative text labels for icons. Alternative text labels aren’t visible onscreen, but they let VoiceOver audibly describe what's onscreen, making navigation easier for people with visual impairments.

Navigation Bar and Toolbar Icon Size

Use the following sizes for guidance when preparing custom navigation bar and toolbar icons, but adjust as needed to create balance.

Target sizes	Maximum sizes
75px × 75px (25pt × 25pt @3x)	83px × 83px (27.67pt × 27.67pt @3x)
50px × 50px (25pt × 25pt @2x)	56px × 56px (28pt × 28pt @2x)

Tab Bar Icon Size

In portrait orientation, tab bar icons appear above tab titles. In landscape orientation, the icons and titles appear side-by-side. Depending on the device and orientation, the system displays either a regular or compact tab bar. Your app should include custom tab bar icons for both sizes.

Attribute	Regular tab bars	Compact tab bars
Target width and height (circular glyphs)	75px × 75px (25pt × 25pt @3x)	54px × 54px (18pt × 18pt @3x)
	50px × 50px (25pt × 25pt @2x)	36px × 36px (18pt × 18pt @2x)
Target width and height (square glyphs)	69px × 69px (23pt × 23pt @3x)	51px × 51px (17pt × 17pt @3x)
	46px × 46px (23pt × 23pt @2x)	34px × 34px (17pt × 17pt @2x)
Target width (wide glyphs)	93px (31pt @3x)	69px (23pt @3x)
	62px (31pt @2x)	46px (23pt @2x)
Target height (tall glyphs)	84px (28pt @3x)	60px (20pt @3x)
	56px (28pt @2x)	40px (20pt @2x)

App Icon - Human interface guidelines

https://developer.apple.com/ios/human-interface-guidelines/icons-and-images/app-icon/

Human Interface Guidelines 

App Icon:

Embrace simplicity. Find a single element that captures the essence of your app and express that element in a simple, unique shape. Add details cautiously. If an icon’s content or shape is overly complex, the details can be hard to discern, especially at smaller sizes.

Provide a single focus point. Design an icon with a single, centered point that immediately captures attention and clearly identifies your app.

Design a recognizable icon. People shouldn’t have to analyze the icon to figure out what it represents. For example, the Mail app icon uses an envelope, which is universally associated with mail. Take time to design a beautiful and engaging abstract icon that artistically represents your app’s purpose.

Keep the background simple and avoid transparency. Make sure your icon is opaque, and don’t clutter the background. Give it a simple background so it doesn’t overpower other app icons nearby. You don’t need to fill the entire icon with content.

Use words only when they’re essential or part of a logo. An app’s name appears below its icon on the Home screen. Don’t include nonessential words that repeat the name or tell people what to do with your app, like "Watch" or "Play." If your design includes any text, emphasize words that relate to the actual content your app offers.

Don’t include photos, screenshots, or interface elements. Photographic details can be very hard to see at small sizes. Screenshots are too complex for an app icon and don’t generally help communicate your app’s purpose. Interface elements in an icon are misleading and confusing.

Don’t use replicas of Apple hardware products. Apple products are copyrighted and can’t be reproduced in your icons or images. In general, avoid displaying replicas of devices, because hardware designs tend to change frequently and can make your icon look dated.

Don’t place your app icon throughout the interface. It can be confusing to see an icon used for different purposes throughout an app. Instead, consider incorporating your icon’s colour scheme.

Test your icon against different wallpapers. You can’t predict which wallpaper people will choose for their Home screen, so don’t just test your app against a light or dark color. See how it looks over different photos. Try it on an actual device with a dynamic background that changes perspective as the device moves.

Keep icon corners square. The system applies a mask that rounds icon corners automatically.

App Icon Sizes

Every app must supply small icons for use on the Home screen and throughout the system once your app is installed, as well as a larger icon for display in the App Store.

Device or context	Icon size
iPhone	180px × 180px (60pt × 60pt @3x)
	120px × 120px (60pt × 60pt @2x)
iPad Pro	167px × 167px (83.5pt × 83.5pt @2x)
iPad, iPad mini	152px × 152px (76pt × 76pt @2x)
App Store	1024px × 1024px (1024pt × 1024pt @1x)

Provide different sized icons for different devices. Make sure that your app icon looks great on all the devices you support.

Mimic your small icon with your App Store icon. Although the App Store icon is used differently than the small one, it’s still your app icon. It should generally match the smaller version in appearance, although it can be subtly richer and more detailed since there are no visual effects applied to it.

Spotlight, Settings, and Notification Icons

Every app should also provide a small icon that iOS can display when the app name matches a term in a Spotlight search. Additionally, apps with settings should provide a small icon to display in the built-in Settings app, and apps that support notifications should provide a small icon to display in notifications. All icons should clearly identify your app—ideally, they should match your app icon. If you don’t provide these icons, iOS might shrink your main app icon for display in these locations.

Device	Spotlight icon size
iPhone	120px × 120px (40pt × 40pt @3x)
	80px × 80px (40pt × 40pt @2x)
iPad Pro, iPad, iPad mini	80px × 80px (40pt × 40pt @2x)

Device	Settings icon size
iPhone	87px × 87px (29pt × 29pt @3x)
	58px × 58px (29pt × 29pt @2x)
iPad Pro, iPad, iPad mini	58px × 58px (29pt × 29pt @2x)

Device	Notification icon size
iPhone	60px × 60px (20pt × 20pt @3x)
	40px × 40px (20pt × 20pt @2x)
iPad Pro, iPad, iPad mini	40px × 40px (20pt × 20pt @2x)

Creating option menus

I wanted one of the filter options on the app to be 'categories' these would be popular searches that make it easier to narrow what sort of bake you want to make. Initially I was going to have a list of the types of baked good someone could possibly want to look at however this created a long list with 'pies, cakes, health and biscuits' been just a few of them. I decided instead to broaden the categories so that there wouldn't be too many to show. I decided to stick with just 4 categories and change these to 'sweet, savoury, healthy and gluten free.'



I then realised that there were other dietary requirements I needed to consider such as vegan and  vegetarian. I then did some research into what word/ term would categorise all of these people. I came across the term 'dietary restrictions'
"Someone with dietary restrictions will convey that they are vegetarian or vegan and will expect you to provide a meal that meets his or her dietary needs. Vegan – A plant based diet with no animal products. They do not eat meat, fish, eggs or dairy products."

 

If this was to be clicked on there would be options to click on again to refine it even further.

Initial designs

As the colour scheme for the app is grey, white and yellow I wanted find an suitable image to use for the first page of my app which incorporated these colours. The image I went for was of a lemon tart which I found on a website called The Stiers Aesthetic, I find the image very clean and fresh which is what I want my app to evoke. I wanted the first page of the app to be very minimal in terms of information as to not put the consumer off. I decided to have the logo and name of the app at the top of the page as I find that this is the most important thing, people need to be aware of the name and the logo so that they can find it on their phone and recommend it to friends. I then wanted a section for people to make an account/ log in to the app. Instead of using the standard 'create account'  found on almost every app I wanted an alternative. Whilst doing research into other apps I saw that KitchenStories uses the options 'I'm new here' and 'Ive been here' which I find adds more of a personal touch.







I wanted the app to have a little introduction to it as there are many unique features that require a brief description. Initially I though displaying them in a list format would be okay however after doing this I realised that there is too much information on the page which probably wouldn't get read. I then decided to break each point up and display them all on separate pages which people could flick through and quickly read. The middle image is the design I originally came up with, i put the logo in the same position as the first page to be consistent and I displayed the necessary info bellow this. However the white text was difficult to read therefore I chose to put a little text box behind it to also highlight the information and hopefully make people more likely to read it. I also thought of how usually when you swipe through pages of information there are dots at the bottom of the page to show you how far through you are. I thought this would be useful as it would again encourage the user to read them as there are only 5 simple facts to go through.



Here are the other pages to accompany this, I chose interesting images of delicious bakes to encourage the user to get baking straight away as well as making the pages less boring. The first and third image use both contain icing and berries where as the second and fourth are both a type of pie. I wanted the images to have a bit of consistence without being too obvious. They also all contain a dark background as I think this gives off a more rustic homemade vibe rather than stark white backgrounds and edited looking photos. Throughout I used a friendly tone of voice so that the app sounds more like a community which makes it approachable. In some cases I spoke about 'Whisk' as though it was a person, I thought this would encourage people to use it more and to bake more as they wouldn't want to let Whisk down. As the app has a voice recognition elect to it I thought about existing things like this such as Siri and Alexa and the idea streamed from there.





I wanted the sign up/ make an account page to be encouraging, most apps expect you to make an account for the sake of it or so they can sell your email on therefore I imagine people are less likely to make one. I chose to add a little sentence saying why it is important to make an account, it says 'make an account to access al the useful features Whisk has to offer' again I tried to make Whisk sound more like a person than a daunting app. In this slide I chose to get rid of the app name and slogan ad it cluttered the page too much. Instead I decided to use the Whisk icon which I will probably do a lot through the app in order to save space and not confuse the user.



The sign up page couldn't really be designed in any other way as it needs to look trust worthy and official, I chose to use large boxes which the user will fill in with information. This makes it easier and quicker to read so the user can swiftly get on to making something, another thing that should speed up the process is having the sign up button in yellow so that it stands out and people can press it as soon as their information has been entered.



This is the homepage which will appear when the app has been clicked on, I wanted something easy to scroll through that offers a lot of inspiration. The options were to either have a grid system featuring suggested recipes or a list view. I have opted for the list view as I find this less intimidating for new bakers, too much information could potentially put them off and make them not want to bake. The homepage will work a bit like pinterest and shows the user recipes it thinks they will like based on the recipes they have previously liked and tested. Each recipe listed on the homepage can be clicked on and the step by step instructions can be accessed just like any of the recipes in the app. However if the recommendations are too broad and the user wants to find something a bit more specific they can filter their homepage to only show for example chocolate recipes.



The pop up filter menu will look a bit like this, one of the main ideas from previous talks/ crits is to have a timescale so that baking doesn't eat too much into peoples days. This is the first feature found on the menu, the time ranges from less than half an hour, less than an hour and less than two hours. The menu also gives you inspiration on what to look for by offering a trending section, this idea comes from twitter which has a similar trending section to it. I think this helps people again feel like they are part of a community and that they are interacting with other bakers. The menu is then broken up into two other sections: categories and ingredient. Categories features popular types of baking that are often search for and this is the same for the ingredient section. The whole app is about making baking quick and easy and I think this feature adds to that.

Colour Choice

Popular colours chosen by bakery's 
Green is used a lot as it represents nature, good health and freshness which are all things a customer would like to associate with the brand. However this does not suit calorific recipes as it gives a false impression. Therefore the colour should reflect the type of product on offer.


What colours make you hungry:

The colour yellow makes most people very happy. It’s a cheery color that is noticeable in most surroundings. When people are happy, they are more likely to eat than when they are feeling sad or overly calm.

The colour orange stimulates the brain, which increases mental activity and often stirs up a sensation of hunger. Many healthy foods are orange; butternut squash, carrots, oranges, and pumpkins just to name a few. Orange is a color that makes people feel welcome and when someone is comfortable, eating sounds like a great idea.

The colour red raises a person’s blood pressure, heart rate, and causes hunger to be more prevalent. This is why many restaurants choose to have red table cloths on tables or red accents on the walls. Red is an excellent color to paint the main room of an establishment where food is sold.
 
 

I liked the reasoning behind using yellow and how it is makes people feel happy which encourages people to eat more. This helps my app as putting people in a happy mood would encourage them to bake and have more patience. I want to use limited colour so that it doesn't detract from the images and other content on the app, however using black white and yellow would run the risk of looking like a warning sign therefore I have decided to use grey white and yellow. 

'A light grey is the perfect color to paint a room to create a calm and relaxing environment.' I want the users of the app to be calmed by the colours to reduce any stress they may experience when baking.