saaskit icon indicating copy to clipboard operation
saaskit copied to clipboard

Feature request: auth, stipe pricing, multi-subscriptions, teams

Open scosman opened this issue 1 year ago • 0 comments

Firstly: super excited for saaskit! Looks like you're making an awesome tool, and I'm looking forward to using it soon (finishing up the product, and waiting for your V1). Thanks for building this!

As a potential user, wanted to share a wishlist/thoughts. Happy to chat about any of them.

  • Bring back suprabase auth, at least as an option. Github OAuth really limits which types of companies can use SaasKit. Not everyone is selling to developers, not every development team uses GitHub (and most companies wouldn’t let you buy tools for production work on a personal GitHub account). I really liked that you used suprabase auth. If you really want to build your own, I more options are needed imo: Google OAuth, Msft OAuth, and password (but we’re quickly starting to re-implement suprabase auth…). This one is likely a deal breaker for me and my project. The ideal UX is a create account page with set of options (that I can configure): password, Google oauth, Msft OAuth, GitHub oauth; then login page takes email address, and shows you which option you used (since people forget).
  • Support Stripe's embeddable pricing page instead of a custom page. They have pretty deep customization, which ties directly into stripe. Would be nice to use that instead of reinventing wheel. P2 but nice to have and might save work. Also happy to build this myself.
  • Multi subscription support: one customer might want to buy several subscriptions and admin them through a single login. For example, a business owner with multiple locations might want: store 1 gets premium sub, store 2 gets basic sub, store 3 gets small sub. From UX POV: the account page becomes a list. It looks the same as it does now, but there’s an “add subscription” button. If you have several, you get the ability to name each subscription in a “manage sub instance” page. I’d likely add custom per-subscription config on top of that with demo KV, but it would be nice to have the data structure be a set of subscriptions by default. The ENV var controlling “multi-subs-per-account” should probably default to off, but would be nice if the data model supported it out of the box.
  • V2: organizations/teams. Add people to teams, with roles (developer,admin, etc). BulletTrain has great support for this. I get it’s not a V1 thing 😀

scosman avatar May 25 '23 15:05 scosman