🗂️ Planning and Sorting Development Priorities
In my previous post I shared how I picked up an old hobby, Cooking, which aided in giving myself a well-deserved break.
This break helped me to prevent myself from burning out by jumping to React Native Mobile Development project right after MERN Web Development project.
During the planning phase of the Mobile Development project, which was before the break, I started building a “What-To-Do and How-To-Do” list as I always do with my projects.
The list is based on the deadline which was approximately a month (since Mobile Development was completely new to me!).
It goes like this:
Do I need to build a refined app or a prototype and show that I can learn Mobile Development? - Prototype now, Refine later.
Is the knowledge from React transferable? - Transferable
⏰ (This is where the complication started)
Do I need to build a new Backend or optimise the current Backend to accommodate Mobile Frontend?
If I need a new Backend, what is the most efficient way to get an automated Backend with authentication, error-handling and database integration and Edge functions to implement custom business logic?
🕳️ (Diving down the rabbit hole)
Most appealing Backend-As-A-Service platforms - Supabase and AppWrite
Will GraphQL be useful with refined data fetching from the BaaS platform?
🔥 (Burn-Out point reached)
Learn these technologies and build a basic app.
Finally implement the skills in the Symptom Checker Mobile application.
Although these technologies are a great addition to any upcoming developer's skill set, the timing was not great and the project did not require such finesse.
Hence, I opted to think about it rather than jump into it.
The Breakthrough
(Glad I took that break! This is EXACTLY why I could come out of that rabbit hole! List continues...)
There is already an existing Backend.
It has basic authentication, error-handling, database integration and a clearly defined business logic.
It has a Layered MVC architecture with clear separation of concerns to keep the codebase maintainable.
I developed to showcase my skill.
Why don't I not reconfigure it for the Mobile Frontend and use it as a Shared Backend?
These questions simplified the planning process for me even though I had to take a dive down the rabbit hole!
I believe it is a vital part of the planning process to know what to do and what NOT to do :)
Cheers and have a good one everyone! 🥂
Thanks to my cat and The Big Bang Theory to help me display the ideal planning process! 😁
Top comments (0)