Crunch the frontend

In the previous article, I talked about the different things that I tried and how I came up with an initially deployment strategy of hosting a PWA on Google PlayStore using the TWA technology

Let's talk about the work that was done on the project so far.

Note that the date of this writing is Aug 16th.

Day 7(Aug 9th) to Day 9(Aug 11th)

In this period, I started by deleting some of the junk react native code that I added to the project when trying experimenting merging both react native and next js in the same project.

After that, I went on the implement components for the connections, notification, settings and events page. Previously I had done the empty states of these pages but now I implemented the page with content.

Note that since we do not have a backend api yet all of these are just staitic dummy pages.

Also whent on to create modals that would allow users to edit their profile and invite people to the application.

Day 10(Aug 12th) to Day 11(Aug 13th)

These 2 days were weekends and since I had made good progress in the project, I didn't touch it at all and used that as an opportunity to catch up with friends.

It is very important to have maintain this balance. If not one is at the risk of burn out.

It was also an opportunity to relax my mind and take a break everything

Day 12(Aug 14th) to Day 16(Aug 17th)

I didn't do much on these days because I fell ill on Aug 15th and I am currently on medication while writing this.

However, the current plan is to test out that deployment assumption and convert the app to a PWA before moving forward.

I would like to test that idea as early as possible so as not to be surprised when I am actually ready to deploy.

Next steps

If I can do create the PWA quickly then I would start working on the backend.

My strategy there is to comsume the API as I create them.

This is the list of things that the API should be able to do:

1.Authentication
a. Login with Google
b. Login with Password and Email
c. Signup with email and password

1. Create,Update and Delete Events
2. Send connection request
3. Accept connection request
4. Remove connection
5. Send emails to users: a. Setup email sending with AWS SES b. Create templates for Authentication c. Create templates for upcoming events reminder d. Create templates for
6. Send emails when: a. User registers b. Beginning of the month with a list of upcoming events for that month
7. User can edit profile

Looks almost like I haven't even started

Conclusion

Had a bit of set back with the illness but hopefully I'll be back very quickly and conver more grounds in this one