Simple timetabling app for university students

We are looking for a developer to create a very simple timetabling app for university students. Please include the app’s name— LifePlanner— in the interfaces along with our brand colours of purple (#864cbf) and orange (#F18F01), with snow white (#fffafa) text. Please use the SF Pro Bold font (available at https://developer.apple.com/fonts/)

The app will center around 4 key if/then conditions, and the user flow will consist of 5 main screens as shown by our rough sketches attached.

Screen 1: basic login screen (email/password/social login)

Screen 2: user is prompted “what do you have going on this week?”, and then is shown a horizontally-swipeable daily calendar, where he can add (+) events for the upcoming week.

- When adding an event on a specific day, user must input:
- Name of event
- Time of event
- Type of event

- There will be 4 types of events for users to choose:
- Sports
- Class
- Clubbing
- Meal

Screen 3: loading screen saying “planning your life”, while algorithm matches conditions.

- Conditions are:
- If sports → then stretch 1 hour before sport, and eat 1 hour after sport
- If class → then cover asynchronous content 24 hours before class, and make revision notes 1 hour after class
- If clubbing → then drink 2 hours before clubbing, and sleep 30 mins after clubbing
- If meal → then buy ingredients 1 hours before meal, and clean up 30 mins after meal

Screen 4: user is prompted with their newly filled-up timetable, in the form of the same horizontally-swipeable daily calendar from screen 2. They can scroll through each day and see what their schedule is like based on the events they added earlier. For example, if user added the class-event “global sourcing lecture” for 9am on Monday, then his schedule will show “do global sourcing asynchronous content” on Sunday 9am, and “make global sourcing revision notes” on Monday 10am.

Screen 5: finally, user will be prompted with the question “can you manage this schedule?”. If yes (✅), then user will be taken back to screen 4. If no (?), then user will be taken back to screen 2.

Please refer to the sketches below for context. Alternatively, if you require more context or guidance, please feel free to contact me and we can chat over a voice/video call. Thank you very much.