Subscribe
Sign in
I'm using BT for an upcoming SAAS project and it's been a huge boost for the project. The same sense of "oh wow, I could do so much with this" that I got from using Rails to build that little blog demo they used to have on their homepage I got from using BT for the first time.
In general, it's a moving "up" in terms of abstraction. So instead of working with a single form field helper in rails, or even the form field with a little surrounding elements (like simple form). You start working with the entirety of the UX for an individual form field: label, error text, tooltip, placeholder, explainer text, etc and it's very easy to extend. For example, I built a 'markdown' instructions button that is inserted below the label on any form element it's designated on.
If you're:
- Already a competent Rails Developer
- Building a SAAS
It's pretty much a no brainer in terms of out of the box value.
I've used Bullet Train before it was publicly available and even then, it was amazing. Andrew was super helpful and is moving fast enough to add a lot of value to Bullet Train.
It's the SaaS base you always needed. No need to think about all the fluffs like user accounts, teams and billing. it's all in there. And much more.
This is a no-brainer for any new app, and even to migrate to for many apps.
It's funny when building products.
About 80% of your effort is building your billing engine, team management, permissions, UI elements, etc.
Rarely the core application.
As a result, it's easy to get burned out early and just not launch.
Thanks to BT I don't have that problem anymore.
Out of the box it has everything you need to run a successful SAAS app so I can focus on the main, core feature set of my products.
Additionally, after you buy BT you get access to an exclusive Slack group where you can just DM Andrew any question you have. Phenomenal.
Will be using it for all projects going forward.
Kudos, Andrew.
Starting my project out using Bullet Train has not only saved time, but helped keep us focused on doing things in a "Rails Way" and keep the structure clean. Very happy with the decision to use it.
