Hi,
I’m currently learning and developing a Field Service Application for our engineering company. I know there are many ‘off-the-shelf’ applications we could use, but there are a couple of unique features we’d like to implement, hence going down this route.
Whilst developing, I accidently (some may say luckily) came across a post about WU and the potential costs. This put me on the rabbit warren path of all the posts about WU costs and optimisation. I woke up this morning thinking of ways I can reduce WU (I’m not even on a paid plan yet!).
So here’s my question, am I overthinking/worrying about this?
Our app is going to be small. We have 10 engineers that will be using it. Sure, we might scale up in the future, but that’s where we’re at now. Will my WU even come close to becoming anything to worry about for an application so small?
In my opinion, it’s good to plan ahead. You’re not overthinking it.
My colleague told me something that rang true to our current situation. Bubble’s great for testing concepts & testing out the market.
If you’re certain that you won’t outgrow your needs (which is hard to imagine, because there definitely will be new features, etc. - but what I mean is nothing major), then Bubble’s a good fit for you.
If you’re planning to stay for the long run & is worried about WUs - there are also workarounds that the community has graciously shared in the forum. Be prepared that these solutions won’t be as straightforward is all.
Also, it’s a good thing to start your app with this in mind. This means that you’ll at least try the best approach to minimise WU usage from the start. You’ll have less headaches in the future.
1 Like
I appreciate you taking the time to post.
I’ve read the workarounds, which seem useful, but this just heightened my anxieties around it to be honest. The reason I’m building it on Bubble is the ease and simplicity of it. I think if I need to start making API calls to external DB’s, then it will take away this ease.
I’m assuming that when presenting information in a RG that is held in an external DB, it isn’t as easy as saying ‘do a search for…’?
I don’t think you’ll even come close to using the 175k WU alotted each month on the cheapest paid plan. 10 engineers, assuming 21 work days a month, they’d each need to be interacting with the app (creating things, updating things, etc) enough to accrue >800 WU/day each. Building with best practices, that’s a LOT per user per day. But even if they used double this, you could add another 200k in WU/month (so 375k total) for another $29/mo. I’d recommend building in Bubble, setting how the WU metrics land, and optimizing from there - but I think you’ll be relatively fine.
2 Likes
That was my original thought after doing some rough calculations. That’s why I posted this thread to get some insight from users much more knowledgeable than me!
I appreciate you taking the time in to reply to me- it has given me some reassurance.
1 Like
Just for reference too, we currently spend ~£650 per month on our current software which this will be replacing.
Don’t worry about it.
Of course optimise if able and convenient, but consider if the time investment is reflected in the cost savings. I don’t know what your app is doing, but with 10 users, I’d be surprised if you’re on more than the starter plan…
2 Likes
Thanks, George. I’ve noticed your posts with regard to optimisation, so I’m grateful for your feedback.
I think I’m going to push on. After looking into it further, I think the worst case scenario would still realise a slight cost-saving from what we currently use (although my time isn’t factored into this as I’m developing it for personal learning and development in my own time).
I think worst case, we’d be on £32 a month starter plan, with £99 in WU with a tier 2 addon. We’d still be saving over £500, an I don’t think we’d be anywhere near 900k a month, even if we doubled workforce.
1 Like
100% George. Some folk get very wrapped up about WU optimisation.
@paul.wilson I’d expect your most valuable resource was your time & headspace to develop your app and that is the resource to be most concerned about. Sure - any easy sensible optimisation - that’s simply good practice to follow in your build.
In any case @georgecollier will likely create an amazing automatic AI WU analysis tool that will tell you exactly what is wrong and probably automagically fix it in the near future 
1 Like
