Direction of wasp-lang
Had tinkered around with it for a week. Like the abstraction done by wasp but thus far I do see a bunch of hurdles for people that want to bring this to actual "saas" level like the direction Vercel is heading. Or maybe I'm wrong and that this is merely a starting point for saas creation and that people would have to break away from the abstraction once there is enough traction for them? Anyway curious on a bunch of stuff below
- having slightly more access to abstractions created
Abstraction is good but sometimes at a cost
E.g, like the oauth process flow is hidden from us, would be better if they are created and can be modified if needed in the template (possible to put up disclaimer or something on modifying it). Case in point, wanted to modify the loading screen that is waiting for the auth callback, or the callback path or password requirements etc
- Localization support or strategies
I think this would bring in even more awareness to the framework those helper components would need to be updated as well I guess
- Support for saml/sso or bring your own provider
I would imagine an saas that deals with b2b would need to have this to login from client's okta or something. This might be a deal breaker for consideration when really building a saas startup
- Feature flagging strategies
Coverage of recommended strategies for them (in doc or something ) for rolling out features or a/b testing (like an actual saas)
- having slightly more access to abstractions created
Abstraction is good but sometimes at a cost
E.g, like the oauth process flow is hidden from us, would be better if they are created and can be modified if needed in the template (possible to put up disclaimer or something on modifying it). Case in point, wanted to modify the loading screen that is waiting for the auth callback, or the callback path or password requirements etc
- Localization support or strategies
I think this would bring in even more awareness to the framework those helper components would need to be updated as well I guess
- Support for saml/sso or bring your own provider
I would imagine an saas that deals with b2b would need to have this to login from client's okta or something. This might be a deal breaker for consideration when really building a saas startup
- Feature flagging strategies
Coverage of recommended strategies for them (in doc or something ) for rolling out features or a/b testing (like an actual saas)
