Interview with the manager
The manager brought a task - to create an application for travel on public transport in the city of Taganrog. He and the customer discussed the functional requirements in advance. Our task was to design the application, make it reliable, convenient, available for downloading from stores and provide its support

We did a sync, assessed what we could and couldn't do, and discussed everything with the manager. After receiving preliminary approval, we broke the task down into smaller ones, prepared, and got to work.

Looking ahead, I want to say that the project was successful. We worked harmoniously, meeting all deadlines, it was successful due to several factors:

1. Team atmosphere
2. The team consisted of competent and open employees who were not afraid to ask questions, yes, there were many stupid and not so stupid questions, but no one judged or teased each other, and we quickly resolved every ambiguity
3. Focus
4. We focused on working on the project, without switching to other tasks. We defined the time, divided it into sprints and fully focused on the task
5. Communication
6. There was clear and timely communication with the customer. We promptly agreed on issues such as the source of data and the necessary functions. Our manager clearly clarified all the details, and we quickly received the necessary answers

So we know the functionality, we know the deadlines, the team is here, let's go

What's going on and what's important about it?

Since the product is new, it doesn't have any users yet, which means we can't ask them about problem areas and points of disconnection. And the application itself doesn't sell anything, but rather provides assistance to users, solves the problem of ease of travel by transport

So the preparation phase starts with a small secondary research phase. I take some time to look at existing apps, see reviews, what users praise, what they criticize

It is clear that here we already have a pre-agreed functionality, and it is unlikely that we will not be able to agree with the customer that this or that function would be removed. But the principle of operation and display itself must be looked at

I sketched out a map of the app, and then moved on to designing it on paper. I sketched out the main screens and thought through an understanding of how the main elements should be roughly arranged on the screen. Usually, I rarely undertake to do this on a sheet of paper with a pencil.

Wireframes.
The next step was to transfer the sketches into an interactive environment. A more conscious understanding of where the buttons should be located, as well as what sections should be present in our application, appeared.

Based on the prepared screens, I prepared a user interaction map with the application, where I showed all the transitions. The main screen was the main one, since it was something like a control panel for all the functionality. Well, it displayed cards, payment cards and the ability to top up an account, binding, etc.

Of course, there was no system design and component base in this project, but there was the Book brand, which is not bad. And there were colors, logos, font, and this is already good. We used Material Design libraries and if something needed to be podcasted, we quickly talked about it in the chat. So step by step we assembled our sections

Second iteration

A selection of application screens

We managed to deliver the project on time, and all participants of this project were satisfied with the result. The application works to this day and the company provides support. Of course, over the past time, comments and wishes have appeared in the stores - which must be taken into account, but let this remain as a legacy to other designers