BeAlive | Devpost

Start up screen
Sign in / route to sign up page
Authentication screen
main feed displays all latest posts by friends and contact
challenege creation screen
main feed displays latest posts by friends and contacts
Commitments screen shows which challenges you are commited to
profile screen where your able to logout and change your profile picture and edit contacts
import contacts screen where your able select which friends you want to share challenges with

Inspiration

We all make promises to ourselves to study harder, stay consistent, hit the gym, or pass that course on the first try. But most of the time, those promises fade because no one’s watching, and there’s no real accountability.

At the same time, as life gets busier, we slowly drift away from the people who used to be closest to us. We still care, but our interactions become fewer, smaller, and less meaningful.

We wanted to build something that brings people back into each other’s lives in a genuine and engaging way. On BeAlive, your friends can show support or doubt and both can push you to take action. Unlike other social platforms where hate is just hate, here it actually fuels motivation.

It’s about being involved not just posting filtered highlights, but sharing what you’re truly trying to achieve and letting your circle be part of that journey. Whether your friends are cheering you on or doubting your commitment, everyone stays engaged, invested, and a little more connected.

We wanted to create a space where commitment feels real, friendships feel active again, and every small win is shared.

What it does

BeAlive is a social accountability app that turns your personal goals into interactive challenges your friends can join.

You start by signing up with your phone number via OTP and setting up your profile — name, username, and profile picture. Then you sync your contacts so you can instantly connect with the people who matter most.

From there, you can create challenges that reflect what you’re working toward. Maybe it’s “I’m going to pass this course on my first try — commitment $5” or “I’m hitting the gym every day this week.” You set a time limit for your challenge like 7 days and post daily updates with photos or proof to show your progress.

Your friends can vote “Yes” or “No” and back their choice with the same amount. It’s about proving people wrong, staying accountable and connected. BeAlive gives you a reason to show up every day and a circle that actually cares whether you succeed or not depending on how they backed your challenge. The result is a feed full of commitment, motivation, and connection where you’re not just scrolling through random posts, but watching your friends grow, challenge themselves, and stay involved in each other’s lives.

How we built it

We built BeAlive as a mobile-first app using Expo + React Native (TypeScript), providing seamless navigation and a clean, consistent UI. Phone number OTP authentication is powered by Supabase Auth on the client, allowing us to ship secure sign-in quickly. To iterate rapidly on core product mechanics feed, YES/NO “investments,” and commitments we used typed domain models and mock data in local state, while integrating proof photos via expo-image-picker for camera and gallery capture. The frontend is organized with modular components and screens using TypeScript for reliability, and the backend is implemented as a FastAPI service, ready to handle challenge creation, feed endpoints, and future persistence with Supabase.

Challenges we ran into

The scale of this project pushed us harder than anything we’ve built before. From 10 AM to 7 AM the next day, we worked nonstop designing, coding, debugging, and connecting every moving part.

One of the toughest parts was finalizing the UI/UX flow finding a way to make interactions feel meaningful and social without feeling like a gamble. On the backend, we had to design a scalable database schema and enable Row Level Security (RLS) correctly across multiple Supabase tables and buckets, which caused several authentication and policy conflicts along the way.

We spent hours debugging Supabase storage bucket permissions, handling signed uploads for posts, and ensuring that only authorized users could create or update their own objects. On the frontend, challenges included building modular components that stayed performant while avoiding excessive reloading from endpoints, structuring navigation cleanly, and keeping state synchronized with minimal lag.

Implementing secure OTP authentication, integrating FastAPI endpoints, and connecting all layers UI, API, and database within a 24-hour window tested every bit of our teamwork and technical ability. We didn’t sleep much, but by the end, seeing everything come together made it worth it. We walked away exhausted but proud, having learned more in one day than in weeks of normal development.

Thanks for listening :)