frederik_diamond on Nostr: **Code backend before coding frontend** When I start working on a new app idea I ...
**Code backend before coding frontend**
When I start working on a new app idea I have, I always begin by designing the UI in Figma. It’s a good way for me to brainstorm things like which features the app should include and get an idea of how I want the UI to look.
After the brainstorming and getting a rough idea of the UI, I start building the frontend. This is the part that I really want to change when I start a new software project.
I have this tendency to immediately begin working on the frontend. I think it’s because it comes easily to me. You know, to design and build a pretty UI.
But I think it would be beneficial to change, so that instead of starting with the frontend, I should begin with the backend once the brainstorming is done.
That way, I can quickly find out which features are tough to implement. That’s valuable information, because there’s no reason to build the UI for a feature that turns out to be too time-consuming to implement.
This is something I experienced when I was working on a macOS app that was supposed to control volume per application (exactly like how the Windows volume-mixer works). I had designed and built the UI, and personally, I think it was looking really good. But when it came time to actually implement the features, things started going downhill.
Turns out, that the necessary APIs are closed source, and getting it to work required a lot of low-level C++ code. I barely have any experience with C outside of the 'Embedded Software' course I am doing this semester, so it was way out of my league.
When I start working on a new app idea I have, I always begin by designing the UI in Figma. It’s a good way for me to brainstorm things like which features the app should include and get an idea of how I want the UI to look.
After the brainstorming and getting a rough idea of the UI, I start building the frontend. This is the part that I really want to change when I start a new software project.
I have this tendency to immediately begin working on the frontend. I think it’s because it comes easily to me. You know, to design and build a pretty UI.
But I think it would be beneficial to change, so that instead of starting with the frontend, I should begin with the backend once the brainstorming is done.
That way, I can quickly find out which features are tough to implement. That’s valuable information, because there’s no reason to build the UI for a feature that turns out to be too time-consuming to implement.
This is something I experienced when I was working on a macOS app that was supposed to control volume per application (exactly like how the Windows volume-mixer works). I had designed and built the UI, and personally, I think it was looking really good. But when it came time to actually implement the features, things started going downhill.
Turns out, that the necessary APIs are closed source, and getting it to work required a lot of low-level C++ code. I barely have any experience with C outside of the 'Embedded Software' course I am doing this semester, so it was way out of my league.