Inspiration

We've all been there-- finishing dinner with a large party and the bill comes scrambled with items and prices. The previous option would have been to take thirty minutes reading through and manually organizing everything before asking your friends to send their portion of the bill at their earliest convenience-- but look no further.

What it does

Splitting bills shouldn't be so hard. Whether you're out grocery shopping, eating, or at any recreational events with a large party, itemizing a receipt is a chore. MOMO aims to make this process as seamless as possible. Simply by taking a photo of your receipt, MOMO will automatically parse each item and allow you to simply select who pays what, then request the funds. Finally, you have an easy interface to reflect on past group transactions which are still pending. Through this, we aim to bring additional convenience to the community.

How we built it

As a team, we collectively experienced similar user stories to decide to tackle this issue. Starting off, our designers were able to generate prototypes in Figma. Meanwhile, our developer team started to lay out the foundation for our tech stack. This app was built in React-Native/Expo in the front-end to support mobile development, with our backend in Flask.

Challenges we ran into

Some challenges we ran into include React-native compatibility issues and difficulty in implementing front-end UI in a timely manner.

Accomplishments that we're proud of

Our most satisfying accomplishment was to see the receipt be functionally processed and parsed into the proper list of items. In addition, our design team created high-quality prototypes.

What we learned

Our team felt inexperienced in the realm of mobile/React Native development. Towards the end of the project, each contributor grew in their own skill sets such as designing styled UI, mobile implementation, backend API integration, etc.

What's next for MOMO

  • Allowing integration with existing money transfer apps
  • Allow splitting through local proximity instead of contacts
  • Hosting/storing transactional data history
  • Suggest promotional places for large party activities
Share this project:

Updates