The problem Karten solves

Crimes are surging day by day. That's where Karten comes into play. This application has a blend of unique features like the safest route to help women commute safely, even the celebrities, travelers, money loading vehicles, and many more. It plummets the risk of unsafe traveling to a greater extent.
For instance, most rape cases in India are committed on road. The USA has high gunshots deaths. These localities can be avoided while traveling using Karten by navigating them through the safest route.

There are many accident detection hardware available on this planet, but none like our software-based systems. This makes it cheap for the common man who drives a low-priced vehicle that is not embedded with this much-needed feature. You need not own a Telsa for that! Karten comes into play. Followed by gyroscopic analysis and location tracking, the desired results are achievable. People are reluctant to buy expensive hardware for such use cases.

Imagine, you have been stuck on a highway at night with your car broken down and none provides aid. To spice it up, your network is also down. Don't worry Karten saves the data of nearest garages (like offline maps, phone numbers) by using garage caching. Thus will be of great help while facing such situations.

The most accoladed feature of the app is to establish a connection between Karten users in each other's vicinity. This can be done with graphing. The main use of this feature is to send an accident SOS to your family, or friends if your phone is destroyed. Moreover, this can be used to monitor driving patterns in a particular region.
That sums up Karten!

Challenges we ran into

The initial challenge faced was due to the lack of research available in this domain, because our application is unique. We struggled a lot to plot the safest route which was never implemented. It took us six hours to get to the point of making it workable. Flutter recently has migrated to null safety causing major troubles. We coded the entire application with targetSDK version as 30 and later migrated to 31 which made it havoc. But finally, we got it to work by migrating all libraries to null safety. With a diligent outlook, we were able to code the 2 major features in just 24 hours.