The problem Claim.it solves

Our app Claim.it aims at reducing the effort from bank's end wrt the vehicular insurance claim investigation and claiming procedure.

Currently banks hire investigators with the sole job of investigating the filed reports. The investigator goes works diligently to find out the middle ground for bank and the claimer. Many a times cases end up in court where both claimer and the bank incurs losses. Furthermore, the banks have to deal with multiple fraudery cases wherein the claimer tries to claim insurance for personal gains. Investigations in such cases lead to losses wrt both time and money. To counter this scenario we introduce Claim.it, an app that aims to simplify the process.

We utilise a few sensors such as accelerometer, gyroscope, GPS etc. to generate the required details pertaining to the accident. Furthermore, we add a 360 degree camera to capture 1 minute worth of buffer video which would be stored directly on a distributed storage solution network (to make sure that the data is not held by a single entity, banks being the entity in this case). To further keep things transparent, we generate the hash of the video and store it on the blockchain network. Thus, the video can be trusted to untouched post posting.

Claim.it is therefore a simplified approach to claiming vehicular insurance both for the claimers and the banks. It reduces the losses incurred by the bank by a significant margin and helping the authorized personal to make correct decisions based on the accident report generated by Claim.it!

Challenges we ran into

We experienced various challenges while developing the application. However, our major concern was the internet connection itself. IIITA makes use of proxy nets while we're used to more free PEAP based solution. We therefore had to add proxies everywhere and we could not connect phones with our laptop to check working APIs locally. This made us develop backend and the application without sync. What frustrated us further was the inability to connect to Google Cloud Services, Azure and AWS VMs. At the end, we could not connect the frontend of the app with the backend while having both sections working as expected. Furthermore, we could have added multiple additional features to the app to make it feature rich.

Keeping proxy aside we did not face any major issues, only a few subtle ones. We faced certain issues relating to simulation of the android application. We were able to overcome them in no time. Other than that, we faced problems while installing packages while developing the product. This was mainly due to the proxy settings as well.