The problem Trip Companion solves

There are many instances when we fail to have a companion in our journey. Trip companion helps you to find the right partner (or friend :)) to travel along in any long mundane journeys or accompany you in events. All the users in our platform are anonymous with sharing the verified information that they want to share. The travellers can choose companions using their shared information and experience. So essentially trip companion helps in,

1. Finding Travel Partners: Many people prefer not to travel alone but struggle to find compatible travel companions. Trip companion match travelers with similar interests, schedules, and preferences, making it easier to find suitable companions for trips.
2. Enhancing Experiences: By finding a companion using our platform can enhance the overall travel experience by providing opportunities for shared memories, experiences, and adventures. Having someone to share moments with can make trips more enjoyable and fulfilling.
3. Local Insights and Knowledge: Travel companions who are locals or have previously visited the destination can provide valuable insights, tips, and recommendations, enriching the travel experience and helping travelers discover hidden gems.
4. Anonymous social Connection: Traveling alone can sometimes lead to feelings of loneliness or isolation. By connecting travelers with companions, our platform foster social connections and facilitate the formation of friendships, both during and after the trip.

Challenges we ran into

So to keep the users anonymous and also verify their authencity like age and gender with revealing any other details, we used anon adhaar.
While integrating anon adhaar with our application, we ran into a few problems. Essentially, while installing anon adhaar sdk, we were getting many webpack issues, and we tried to resolve them but it lead to hell of recurring errors. We discussed these issues with the anon adhaar team and upon discussion they suggested us to use yarn instead of npm and some other technical fixes. So after a lot of different trail and errors, we were able to integrate it completely with our application. Also, verification of adhaar was taking a lot of time and computational resources, but after upgrading to their recently launched newwer version, it got fixed and reduced both time and memory.
Secondly, we were unfamiliar with The Graph and GraphQL language initially, so there was a learning curve for us. Every time we needed to update the contract, we had to redeploy the graph repeatedly, which was quite tedious.