SkyFlare - A Unified Development Framework

We decided to create our own framework to rapidly build out working prototypes that could be easily improved and expanded to be production ready. Sky is the backend API-driven backend and Flare is the frontend API consumption coordinator. Sky doesn't require Flare to be expressed. Flare doesn't only work with Sky. By separating concerns, each can stay focused on their primary purpose without requiring coordination in their development. Because the vast majority of all B2B SaaS applications are thin application layers for data relationships, the data relationship should be the center column of a good B2B application. Deciding to use convention over configuration, we started with the database design to determine the application architecture and the interfaces. Coupled with an auto-create endpoint, Sky can build up a basic CRUD application in seconds. Because Flare doesn't attempt to replace native browser APIs but to extend them for the purpose of more easily managing API consumption, Flare can manage API consumption atomically and repeatedly with less memory overhead and a minimum of configuration. Flare configuration is achieved through the use of flare-* attributes which allows for "micro-configurations" and easy tooling for complicated API flows such as remote loading data, template hydration and dom injection.

SkyFlare has already been used in multiple projects with clients and has shown to be a more performant, expressive framework in the narrow context of B2B multi-tenant, SaaS applications. A single developer working with SkyFlare has been able to create and manage 14 applications in under 3 months. Clients have been amazed and pleased with the breadth of the working prototypes created and have been able to quickly approve projects that have 30% lower up front costs.