The problem Resolva solves

In organizations where there is only one point-of-contact with the administration or the upper management, the middleman faces a lot of difficiulty in listening to everyone's complaints and grievances and then also deciding which ones are the most important or hot ones, and which ones can be put on the shelf for a while.

In offline systems, the middleman has to craft those grievances into a letter by their own skill and has to be unbiased and immaculate with their summary. This is often a tedious task and prone to errors.

Our project aims to reduce the work of those lone soliders who try their best to communicate the grievances of their community or society to those in charge and capable of solving problems. The AI assisted tools greately streamline their flow and make them more efficient than usual. It also helps them make more efficient and to-the-point letters.

This also means that users are happier because more of their complaints or grievances are being relayed to the upper management.

Challenges we ran into

• Since we were creating a B2B software as a service for other organizations, we had to be thorough with out onboarding process and how users (and organizations) would be signed in and/or created. We had to spend a good chunk of time outlining the flow diagrams and understanding where the user lands after signing in. But with enough perseverance and remembering our Software Engineering lessons we managed to get through.

• The users also had to be checked in twice - so there were essentially two sign in steps, and we had to make sure that the first Layer didn't accidentally breach into the second, and how we can seamlessly switch between organizations.

• Because of the structure of this project being a SaaS, we had to build an App inside the framework of another App, both which we created, and hence routing was especially key. We had some minor shocks when stuff got routed incorrectly, but with a clear mind and careful testing we were able to clean out the routing problems.

• Because our code was being developed on multiple fronts, we had to be especically careful about keeping our commit history clean and not run into any nasty merge conflicts. But by using stashing, GitLens and communicating with each other properly, we were able to avoid such mishaps. We also adopted Conventional Commits standards like feat, fix, refactor and others to ensure we know what code was being pushed and what achieved what.