Good question Steven!
My steps have been:
- Database
- Create the database definition in a sql file
- Realise all the data structures that could be improved and iterate on this.
- Create stored procedures that do some fundamental actions like a user’s data creation on sign up.
- Getting to Know Wappler
Spend 2-4 weeks just getting to know Wappler and Bootstrap using a bunch of test pages with focus on:
- Setup of environment - local/remote database/server setup
- How Bootstrap structures work and manage the layout.
- How all input types work
- How data flows GUI-database and back for all types of information.
- How the design and styles tabs work.
- My Design in Wappler
Once I really understood how Wappler and Bootstrap works, I then started designing the look, feel and structure of my app. I spent ages and ages coming up with and documenting consistent naming conventions for id, class etc as this is more critical than in Bubble where you can change names so much more easily.
- Go Build!
Now I’m in the “just go build it” phase, where I’m putting all that stuff in place for my design!
Lots of background learning going on to fill in the gaps in my knowledge, especially around hosting and security.
- Database Creator
At the moment I am still in “just blow away the entire database and start again every week” mode as I have no client data to retain… so the database creator wouldn’t have made any difference to my methodology so far but will very shortly!