Connecting dancing people

Macro Architecture
We want to be fast in the market. To do so we always strive for a solution that is fast to implement. We do not optimize things that pay out only in years. Still, we believe that Dancier will be adopted by dancers more and more. So we are aiming for a good balance, between development velocity, maintainability and scalability.
Our System should be as resilient as needed. So in the case of partly broken systems, as much as possible of the user experience should remain intact. + We also try to employ Data Science Tasks right from the start. We want to learn from the dancers to give them the best user experience possible. So we provide all relevant data for such tasks, without impacting operational services.
In general, we will implement

Micro Architecture
Believing that dancier will grow fast, we will permanently have to add new features. This could lead to something like a big ball of mud. So we try to implement each new feature as a loosely coupled module.
We will invest "something" into the interfaces between the modules. But in the module itself, we strive to be as fast as possible. In case a module turns out to be too buggy, we could just rewrite it. See more in the architecture description.

Frontend development
We are not having the capacity to have native apps right from the start (although a Webview-Based Android App seems to be achievable). But our Browser based version should work on mobile devices pretty fine so that we can make "real" apps later.