Everyone,
We are about to embark on a new project for a client. We have read all the pros/cons of SPA, PHP, and Nodejs. We have 20+ years of PHP and 1.5 years of Wappler (all PHP) experience. We love the fact that Wappler removes the “coding” aspect of our projects. Our last Wappler project was a portal system to manage an organization’s group members, it was a win for the client. Our portal had a few traditional form pages but we kind of over did the use of “modals” and have wondered if there was a better way for users to edit and manage data in the portal. That started the ball rolling and looking into SPA for our new project. We liked the idea of “views” instead of pages. That rabbit hole lead to the discovery of Nodejs. And now we are stuck on what to proceed with.
New Project Details:
Our project is a Point of Sale system, eCommerce, and back-office support for a small business. Most POS systems and eCommerce systems out there do not have the strict product requirements our client has. So after 8 years of trying different systems, they want to make their own. We aren’t worried about the eCommerce part, Wappler has great documentation on that. Where we need the advice is what to use to make the POS and back-office parts work smoothly together. We imagine that the POS and BO parts are similar to and Admin Panel application where there are a few key layouts that just have content areas that are loaded. We would like to make the interface feel less website app like and more native app like if possible.
Our Questions
So everyone, what advice do you have for us? Do we stick with PHP and add a little SPA or jump for Nodejs? Does Nodejs work like an SPA (what we saw in routes, appears that it does)? We think that our POS and BO would be their own nested SPAs within a main SPA that manages security and basic user info, would that be correct?
Last updated: