Building an engine that can be integrated in our university management platform Squoolr and making it open source. With the mentality that more brains build better, permitting other developers to share their insights and skills on this will go a long way to scale the project's viability.

What it does

Permits universities or learning institutions to have timetable management module in their school's Information System (IS) without the hassle of having to build one.

How we built it

We build a SaaS with an app for developers to create and manage their schools, subscriptions and api keys, and another app (default ui) for the schools who do not have their IS to use.

Challenges we ran into

Thinking out the architecture of a SaaS product, how to make it such that it'll permit for other developers to integrate, while staying protected.

Accomplishments that we're proud of

Having found how to architect a project for integration on 3rd party apps, organized our first open source app on github, and one that we intend to build on for long.

What we learned

Architecting SaaS projects, and implementing them into functioning,

What's next for RICLY

continue building the engine to be robust, bring in artificial intelligence through genetic algorithms to make the timetable generation most optimal, build a solid architecture around the engine to permit it's existence in as many types of 3rd party apps as possible, make it used nationwide and why not world wide

Built With

Share this project: