MemoryBridge

MemoryBridge is a self-reported mobile application that allows close friends and family to collaboratively preserve memories using a shared map interface. The app enables users to upload photos, attach location, date, and voice stories, and share them within a private circle. It incorporates AI assistance for organizing fragmented memory data but emphasizes human control over AI suggestions.

The product is described as built with Expo, React Native, Supabase, and OpenAI APIs, with an emphasis on privacy and user-controlled AI behavior. The team consists of two members (octopus zhu and Yiqin Cao), who submitted it to the OpenAI 2026 hackathon.

Key commercial due-diligence read: The description provides no evidence of revenue, customers, or traction beyond a prototype built during a hackathon. It is unclear whether the product has moved beyond demo status or if there is any ongoing user engagement or monetization strategy.

The description states that MemoryBridge is a private, collaborative memory map for trusted circles. Users can:

• Upload real photos;
• Attach place, date, and short stories;
• Drop memories onto a shared map as "memory pins";
• React, comment, or add perspectives from others in the circle.

It also includes an AI memory assistant that:

• Extracts titles and summaries;
• Identifies dates, places, people with confidence and evidence;
• Generates follow-up questions when details are uncertain;
• Compares new material with existing stories to return up to three possible matches;
• Organizes drafts without presenting inferences as facts.

All AI suggestions remain editable and reviewable. The app enforces a rule: AI suggests; people decide.

The system is built using:

• Mobile-first Expo and React Native application
• TypeScript
• Clerk for authentication
• Supabase with PostgreSQL Row Level Security (RLS)
• OpenAI API integration via structured JSON schema
• Deno Edge Functions for privileged operations

Not evidenced: whether the product functions beyond a prototype or has real users.

The description states that MemoryBridge was inspired by personal experiences of students who have lived across continents and faced farewells, good memories, and friends scattered around the world. The core idea is:

“What if a map could hold not only where we went, but what those places meant to us?”

This positions the product as a private, intimate way to remember — distinct from public social platforms, which are described as designed for reach, performance, and engagement rather than personal memory preservation.

The positioning evolves from:

1. A hackathon prototype aiming to solve a personal problem (fragmented memories);
2. To a tool that supports collaborative storytelling through shared maps;
3. With AI assistance integrated to help organize and enrich memories, while maintaining human agency.

Inferred: The product is positioned as a niche solution for close-knit groups rather than a general-purpose memory app or social platform.

Not evidenced: No claims about market size, competitive differentiation, or long-term positioning beyond the hackathon submission.

The description states that MemoryBridge targets:

• Close friends who have moved away;
• Graduates;
• Travelers who shared experiences;
• Anyone wanting a more intimate way to remember.

It is described as being for trusted circles, implying a small, private group of people — not broad public use.

Not evidenced: No specific demographic data, usage frequency, or customer segmentation beyond the stated user types.

Inferred: The ICP likely includes individuals aged 18–35 who value personal storytelling and have access to smartphones and shared digital experiences.

The description does not state any business model or pricing information. It only mentions that:

• Privacy is part of the product rather than an afterthought;
• A map belongs to a private circle;
• Non-members cannot read memories;
• Invitation screens do not reveal photos, stories, or precise locations before someone joins.

Not evidenced: No mention of monetization strategy, subscription plans, freemium tiers, or revenue streams.

The app is built using:

• Mobile-first Expo and React Native
• TypeScript
• Clerk for sign-in and sessions
• Supabase with PostgreSQL Row Level Security (RLS)
• OpenAI API via structured JSON schema
• Deno Edge Functions for server-side logic
• react-native-maps for native map interface

Key technical features include:

• Private media storage in Supabase Storage;
• AI processing through structured pipelines;
• Zod validation at client boundary;
• Local demo mode with AsyncStorage fallback;
• Cloud path with real authentication, RLS, and private storage.

Not evidenced: No evidence of scalability, performance metrics, or production deployment beyond the hackathon prototype.

The description states that:

• The app was built during a hackathon (OpenAI 2026);
• It is currently used by a few friends encountered during travel;
• The GitHub repo is private and requires an access request.

There is no evidence of:

• Revenue or monetization;
• Customer base or user growth;
• Product adoption beyond the founders’ personal network;
• Any form of traction or market validation.

Inferred: The product is at a very early stage — likely a prototype or MVP, not yet in production use by external users.

The description does not mention any competitors. It only states that public social platforms do not solve the problem of preserving intimate memories among close friends.

Not evidenced: No competitive analysis, market size estimates, or positioning relative to existing memory or social apps.

Inferred: The space may include photo-sharing apps, travel journals, and social media platforms — but no direct competitors are named or described.

• No traction or revenue: The product is described as a hackathon prototype with no evidence of real users or monetization.
• AI behavior risk: While the system is designed to avoid authoritative AI output, there remains a risk that AI suggestions could be misinterpreted or misused if not carefully managed.
• Privacy and security complexity: Integrating authentication, RLS, and private media storage in a mobile app introduces technical risks around data leakage or unauthorized access.
• Scalability concerns: The product is described as built for a small circle; it's unclear how it would scale to larger user bases or more complex memory structures.

Not evidenced: No evidence of legal, compliance, or regulatory considerations related to privacy or AI use.

1. Has the product moved beyond the hackathon prototype into a functional, tested version used by external users?
2. What is the current user base? Are there any early adopters or pilot groups?
3. Is there a plan for monetization or revenue generation?
4. How does the team intend to scale from a small circle of friends to broader adoption?
5. What are the technical challenges in moving from local demo mode to full cloud deployment?
6. How is user privacy and data protection ensured at scale?
7. Are there any legal or compliance considerations related to AI-generated content or voice transcription?