Hi all,
Since i haven't been working on Laravel for over a year now. Im a little doubting the route i want to take. I'm planning a new small saas project as side project to manage some subscription stuff.
This will be in phase 1 just a web base app and later connected to ios / andoird (react native) app.
Im not sure what i want to use. Since im working on the PWA/Magento/React route anyway its either laravel itself (routes of laravel and blade templates probably with a few react components inside) or a complete SPA (react, next or just react)
What do you guys think the best route is, also taking in to account everything needs to be api-first anyways due to the coming ios/android stuff.
A complete spa will add some complexity and extra development time though
I would use Laravel / Lumen to build the api first approach, so basically thats your backend/API sytem, this way then you can connect either a full SPA or a combination, and then its also set to then use on iOS and other formats. Hopes this helps
I agree that going for an api and frontend separation is the best approach to prepare you for your futher integerations.
I'm assuming this might be a fairly big side project?
If it is, I would suggest at least trying some different approaches in terms of tech stacks on smaller test projects before you dedicate a huge amount of time into this side project. This is because no one is going to know which is more comfortable to use than you trying different approaches yourself.
Also, don't forget to plan ahead. Creating a tech plan before actually developing a project is very benificial.
Please or to participate in this conversation.