I’ve searched through the templates and can’t seem to figure out which would be a good starting point for my Field Service App.
The app will have the following features:
Customer Database
Staff logins with responsive screens for job reports on mobile devices
Stock management and ordering
Job allocation and notifications
Equipment management
Equipment service schedules.
It will run and look similar to other well-known field service apps, such as JobLogic and Tradify etc.
Anybody made something similar and can point me in the direction of the best starting point before I start from scratch?
Personally for something this complex, I would not use a template. They usually end up being more trouble then they are worth. Also, this is a very competitive space with many tools that exist. It would be less expensive and time consuming to use an existing tool but if you do want to venture and build your own – I would spend a good amount of time in the database architecture!
Appreciate your response. I agree in terms of the cost-effectiveness of using an existing product, however, the industry I’m building this for is pretty niche and any ‘off the shelf’ platforms we’ve tried need other systems running alongside it. This is something I’m wanting to eliminate.
Thanks, Jacob. Any support/advice you could give with starting out? I’ve built some basic Bubble apps before, but will need to brush up on my knowledge before getting into this. I’m aiming to have it complete in 7 months (when a current subscription expires), so not a huge amount of time for something this complex.
Understandable. I’ve built a pretty complex bubble app - happy to help you brainstorm and give you some bubble building tips so you can think through how you’ll actually approach building it.
We’re only a small company of 10 employees, but we have ambitions to scale. We have no intention whatsoever of selling this product to anybody else, so we certainly wouldn’t be competing anyway haha. I’d appreciate any help/guidance along the way. I’m currently working on how to structure my database and relationships between data and getting my head around that.
A customer can have multiple sites, multiple equipment which all need multiple parts. The parts can have equivalent parts and all have difference service intervals. The database is going to be tricky to get right!
