I started with what I find interesting in the kitchen, conditionally if I had to buy a toaster or a kettle, which would I choose? I like this aesthetic. A bit toyish and wacky in a good way.

I write a list of ideas and made a small sketch on an iPad. Usually, this is enough for a good prototype; I skip the design stage on wireframes since I can create assets for myself and immediately build the interface as it will be in the final. And since I do everything on standard components, I can save a lot of time, we can customise the appearance and shape of all parts, but at the same time, they retain their behaviour. Such an application must be already much better suited for accessibility and inclusivity.

The common mistake of most companies is the extraordinarily aggressive use of branding elements: typography, colours, logos, etc., But the interface is not an advertising banner but a tool. If the user is already inside the application, why put a randomly coloured interface with an unreadable corporate font?

My logo is an icon that I quickly took from a set of SF Fonts (this is a prototype, and it makes no sense to do everything initially, it is essential to convey the idea); I took the most contrasting shade of blue from the icon and made it the dominant colour that is used on clickable objects throughout the interface. 

Custom font from the logo is used only in the header, which is easy to replace if necessary; most of the interface uses the system font, So I'm sure we can make different locales; a dynamic font and such an interface is easy to port to other platforms and devices in the future,

As you have already noticed, the search filter forms a sentence; the accent colour suggests you can click on it or pull it down for clarification.

Usually, in other programs, we can see preset texts or even texts with pictograms, but this needs to be read and delved into. And if we are cooking that the device is either far away from us or we may have hands that are not completely clean and need to make significant and understandable controls.

I always try to avoid technical abstract things and make controls that say why they are needed.

Here we see:
— selection of the type of dishes according to the diet
— the level of complexity of cooking (from easy to hell kitchen)
— the approximate eating time (here, we do not need a minute hand, so it's faster to choose lunch, dinner, etc.)
— national dishes (when choosing, a very short jingle will sound on a folk instrument so that you can create a pleasant emotional attachment)

🔉 Everything should click as if lego cubes are knocking against each other, and a slight vibration is given through the Taptic Engine.

It looks like a movie cover; this is the second place in the application where we use custom fonts; they can be entirely different for the nature of the dish.

A special detail is that we can change the ingredient with a simple swipe if it does not suit us; for example, I do not eat meat and want to replace it with something without changing the taste of the dish radically. Here I added a tiny visual hint with a protruding ear of a neighbouring component, which is very lacking in standard applications; we just don't know about this gesture.

To order ingredients in the application, there is integration with a local delivery service, for example, Deliveroo. This is good for the user and two or three businesses at once.

All the products have already been selected in the pop-up that appears, and we need to remove the selector from those we already have. Presto!

A video accompanies cooking and the cooking process by points, resembles the calendar interface; the red line is gradually moving.

Since our iPhone is also a helpful tool, we can embed valuable utilities that will be useful to us during cooking, for example, a timer or tips on how to hold a knife correctly,