Hi pchal. We've often been surprised with how flexible Lowdefy is. One can easily build everything from simple websites, public webforms, to complex multi-tenant web apps - which is very exciting.
We decided to limit what we currently market it as to first try and get some traction in a smaller niche for now. However, since resources are limited for an early days startup, we also made this decision based on the following technical considerations.
When designing internal tools, the aesthetics often takes less priority than functionality, thus it's ok and maybe even great if most internal tools look the same, which makes building a great component library a whole lot easier. Also for internal tools you mostly have repeat users, so browser caching helps a lot and thus we can be more lenient on bundle size. When building consumer apps aesthetics and load time is often a high priority, although we have a few ideas to improve on this as well in the future when we have more resources available.
However, if you are building an app where these two constraints is not a high priority, Lowdefy can be a great fit! We really tried to design config schema which can really scale as well.
As far as auth goes, that number 1 on our roadmap. We will be adding OAuth/OpenId Connect authentication, and then you will be able to use services like Auth0, Okta, or any OAuth provider.
We plan on providing our own user service, with group based user authorization that will integrate easily with Lowdefy apps, and offer different pricing tiers to support the needs of business users and SAAS apps.
We decided to limit what we currently market it as to first try and get some traction in a smaller niche for now. However, since resources are limited for an early days startup, we also made this decision based on the following technical considerations.
When designing internal tools, the aesthetics often takes less priority than functionality, thus it's ok and maybe even great if most internal tools look the same, which makes building a great component library a whole lot easier. Also for internal tools you mostly have repeat users, so browser caching helps a lot and thus we can be more lenient on bundle size. When building consumer apps aesthetics and load time is often a high priority, although we have a few ideas to improve on this as well in the future when we have more resources available.
However, if you are building an app where these two constraints is not a high priority, Lowdefy can be a great fit! We really tried to design config schema which can really scale as well.
As far as auth goes, that number 1 on our roadmap. We will be adding OAuth/OpenId Connect authentication, and then you will be able to use services like Auth0, Okta, or any OAuth provider.
We plan on providing our own user service, with group based user authorization that will integrate easily with Lowdefy apps, and offer different pricing tiers to support the needs of business users and SAAS apps.