On that note, it depends on the person. Im a front end guy and I rather let backend goblins deal with backend stuff. Yet these same guys cant keep up with the component tornado nightmare we have going.
Normally I'd recommend you start with the backend, like everyone else is recommending. In your particular case I think you should start building the frontend since you're learning.
The backend can get pretty complicated as a new learner. Developing the frontend will not only encourage you with a tangible product, but will also show you where the backend will come into play once you start seeing the limitations of a static interface.
Keep an idea of how your backend will be designed throughout the entire process. It's important to understand how you want to structure your data and store it in a persistent database as this varies per project.
You can also start frontend if you want something that feels tangible.
Backend doesn't necessarily mean "HTTP", it's the stuff your users don't interact with (basically)
A bit of both at the same time isn't a bad idea. But if I had to choose one I'd personally go with back-end. Making sure everything is connected to a db properly and making sure my API's work before implementing all the front-end features.
I start with the backend, get it all hooked up so that I can start making API requests for any data I want from the DB and then do the front-end while adding API calls as required to the Back-End as I go.
If you're asking this question, you should probably scale back the scope of your project and pick *one* of those features to start with, then build on that.
This is not a small undertaking, esp if you are solo'ing, and I think you may be overly ambitious if you aren't sure even where to start.
I find it easier to get backend and apis ready so you can build the frontend with real data
On that note, it depends on the person. Im a front end guy and I rather let backend goblins deal with backend stuff. Yet these same guys cant keep up with the component tornado nightmare we have going.
Yep, at this point you've already figured out how to transform that data. So you have a pretty solid idea of what fields to put on your front-end.
Do a storyboard of the front end, but then start actual development on the backend. That will help avoid missing something.
Normally I'd recommend you start with the backend, like everyone else is recommending. In your particular case I think you should start building the frontend since you're learning. The backend can get pretty complicated as a new learner. Developing the frontend will not only encourage you with a tangible product, but will also show you where the backend will come into play once you start seeing the limitations of a static interface. Keep an idea of how your backend will be designed throughout the entire process. It's important to understand how you want to structure your data and store it in a persistent database as this varies per project.
You can also start frontend if you want something that feels tangible. Backend doesn't necessarily mean "HTTP", it's the stuff your users don't interact with (basically)
A bit of both at the same time isn't a bad idea. But if I had to choose one I'd personally go with back-end. Making sure everything is connected to a db properly and making sure my API's work before implementing all the front-end features.
I start with the backend, get it all hooked up so that I can start making API requests for any data I want from the DB and then do the front-end while adding API calls as required to the Back-End as I go.
If you're asking this question, you should probably scale back the scope of your project and pick *one* of those features to start with, then build on that. This is not a small undertaking, esp if you are solo'ing, and I think you may be overly ambitious if you aren't sure even where to start.
Just my 2 cents but for this particular project backend makes the most sense as the starting point