Name: Photo Journal App
Availability: InStock

Get started

Ready to build

Build the app you keep thinking about.

Describe your idea. Sanic AI builds the real app, end to end.

Start building See how it works

Built with Appsanic

Photo Journal App

One photo a day, with your friends

A friends-only, one-photo-a-day journal. Each day everyone gets the same shared prompt and answers it with a single photo and caption. The Today screen shows the prompt and a live feed of friends' entries with a streak chip. Tap an entry for the full-bleed photo, reactions, and comments. Your profile holds your streaks and diary as a photo grid. Friends are added by request and mutual accept, which drives the feed. Runs on your own Supabase project (Auth, Storage, Realtime) - no demo data.

One shared daily prompt, answered with a single photo + caption
Today feed of your friends' entries, with a day-streak chip
Heart / fire / laugh reactions and a comment thread per entry
Profile with current + longest streaks and your diary as a photo grid
Friend requests with mutual accept that drive the friends-only feed
Real Supabase backend (Auth, Storage, Realtime) with RLS - no demo data

Use this template

What you can do

A friends-only, one-photo-a-day journal. Each day everyone gets the same shared prompt and answers it with a single photo and a short caption; you scroll today's entries from your friends, react with a heart, fire, or laugh, leave comments, and keep a personal diary with a posting streak. It runs entirely on your own Supabase project, so after forking you connect a backend and apply the schema; until then the app shows a Connect screen (with an optional sample-data preview), and once connected you sign up and everything goes live.

Made forFriend groups who want a simple, honest, one-photo-a-day ritual together.

Answer one shared daily prompt with a photo and caption
See your friends' entries for the day in a single live feed
React to any entry with a heart, fire, or laugh
Leave and read comments on each entry
Keep your own diary of past days as a tap-through photo grid
Track your current and longest posting streaks
Add friends by request and a mutual accept that drives the friends-only feed
Nudge a friend who hasn't posted today's prompt yet

Under the hood

For developers: exactly what is included when you start from this template, taken straight from the template's own code.

Stack

Expo SDK 54React Native 0.81React 19TypeScript 5.9Supabase (Postgres, Auth, Storage, Realtime) via @supabase/supabase-js 2expo-image-picker 17react-native-svg 15react-native-safe-area-context 5.6react-native-web 0.21

Screens

Connect
Shown when no Supabase backend is configured: setup steps plus an optional 'Preview with sample data' button to explore without a backend.
Auth
Real Supabase email/password sign-in and sign-up; sign-up passes a display name for the new profile.
Today
Home tab: the day's shared prompt banner (capture-now vs answered), a day-streak chip, a 'waiting on' nudge list, and the live feed of you and your friends' entries for today.
Capture
Pick one photo with expo-image-picker, add a caption, and post your single entry for today's prompt (one per day, enforced).
Entry detail
Full-bleed editorial photo with the date set in, heart/fire/laugh reactions, and the full comment thread with a sticky composer.
Profile
Profile tab: avatar, current and longest streaks, entry and friend counts, and your whole diary as a tap-through photo grid.
Friends
Search people by name/username, send a friend request, accept incoming requests, and unfriend.
Settings
Edit your profile (display name, username, bio), sign out, and an About panel.

Data model

profiles
One row per auth user with username, display_name, avatar_url, bio, and trigger-maintained entry_count, current_streak, longest_streak.
prompts
One shared prompt per calendar day, keyed by a unique prompt_date, with released_at, text, and entry_count.
entries
One photo per person per prompt via a unique (prompt_id, author_id), storing image_url, caption, capture_delay_minutes, reaction_total, comment_count.
reactions
One reaction per user per entry (unique entry_id, user_id) with kind constrained to heart, fire, or laugh.
comments
Comment threads on entries, each with entry_id, author_id, and a body of 1 to 1000 chars.
friendships
Symmetric friend pairs stored once with a_id < b_id; created only by accept_friend_request, never by a direct client insert.
friend_requests
Pending requests keyed by (requester_id, addressee_id); a friendship is created only when the addressee accepts.
entry-photos (Storage bucket)
Public Storage bucket holding entry photos; writes are scoped to each user's own folder (first path segment must be their auth uid).

Backend

RLS is enabled on all seven tables: profiles and prompts are world-readable; entries are visible only to the author or a friend, and reactions and comments inherit that entry visibility via the entry_visible() helper; all writes are restricted to the owning user through auth.uid().
Friend-only visibility is enforced by the security-definer is_friend(a, b) and entry_visible(user, entry) SQL helpers used inside the entries, reactions, and comments select policies.
SECURITY DEFINER RPC handle_new_user() runs on the on_auth_user_created trigger on auth.users to auto-create a profile and resolve username collisions on signup.
Friendships are never inserted directly by clients: send_friend_request() and accept_friend_request() (SECURITY DEFINER) implement a request-then-mutual-accept flow, so nobody can self-grant a friendship or read another member's friends-only entries.
ensure_today_prompt(text) (SECURITY DEFINER) computes today's date server-side and idempotently creates the one shared prompt row for the day, so a client can't backdate or forge the prompt; there is no client insert policy on prompts.
After-insert and after-delete triggers on entries, reactions, and comments maintain denormalized counters (entry_count on profiles and prompts, reaction_total and comment_count on entries) and call recompute_streak() so the feed never aggregates at read time.
A before-update profiles_lock_counters() trigger forces the counter/streak columns back to their stored values for client (authenticated/anon) updates, so a member can edit display_name/username/bio/avatar_url but can never forge their entry count or streaks.
All seven tables (profiles, prompts, entries, reactions, comments, friendships, friend_requests) are added to the supabase_realtime publication for live feed/reaction/comment/request updates.
Photos live in a public 'entry-photos' Storage bucket with owner-scoped insert/update/delete policies (the first folder segment must equal the user's auth uid). No Edge Functions are used.

More templates

All templates

Social

Social Feed App

An Instagram-style starter: feed, stories, likes, comments, follows, and an activity inbox

View template

Social

Live Streaming App

Broadcast yourself, watch others live

View template

Social

Dating App

Swipe profiles, match, chat, meet

View template

Social

Community Forum App

Topic boards where people post and talk

View template

Built with Appsanic

Photo Journal App

One photo a day, with your friends

One shared daily prompt, answered with a single photo + caption
Today feed of your friends' entries, with a day-streak chip
Heart / fire / laugh reactions and a comment thread per entry
Profile with current + longest streaks and your diary as a photo grid
Friend requests with mutual accept that drive the friends-only feed
Real Supabase backend (Auth, Storage, Realtime) with RLS - no demo data

Use this template

What you can do

Made forFriend groups who want a simple, honest, one-photo-a-day ritual together.

Answer one shared daily prompt with a photo and caption
See your friends' entries for the day in a single live feed
React to any entry with a heart, fire, or laugh
Leave and read comments on each entry
Keep your own diary of past days as a tap-through photo grid
Track your current and longest posting streaks
Add friends by request and a mutual accept that drives the friends-only feed
Nudge a friend who hasn't posted today's prompt yet

Under the hood

For developers: exactly what is included when you start from this template, taken straight from the template's own code.

Stack

Screens

Connect
Shown when no Supabase backend is configured: setup steps plus an optional 'Preview with sample data' button to explore without a backend.
Auth
Real Supabase email/password sign-in and sign-up; sign-up passes a display name for the new profile.
Today
Home tab: the day's shared prompt banner (capture-now vs answered), a day-streak chip, a 'waiting on' nudge list, and the live feed of you and your friends' entries for today.
Capture
Pick one photo with expo-image-picker, add a caption, and post your single entry for today's prompt (one per day, enforced).
Entry detail
Full-bleed editorial photo with the date set in, heart/fire/laugh reactions, and the full comment thread with a sticky composer.
Profile
Profile tab: avatar, current and longest streaks, entry and friend counts, and your whole diary as a tap-through photo grid.
Friends
Search people by name/username, send a friend request, accept incoming requests, and unfriend.
Settings
Edit your profile (display name, username, bio), sign out, and an About panel.

Data model

profiles
One row per auth user with username, display_name, avatar_url, bio, and trigger-maintained entry_count, current_streak, longest_streak.
prompts
One shared prompt per calendar day, keyed by a unique prompt_date, with released_at, text, and entry_count.
entries
One photo per person per prompt via a unique (prompt_id, author_id), storing image_url, caption, capture_delay_minutes, reaction_total, comment_count.
reactions
One reaction per user per entry (unique entry_id, user_id) with kind constrained to heart, fire, or laugh.
comments
Comment threads on entries, each with entry_id, author_id, and a body of 1 to 1000 chars.
friendships
Symmetric friend pairs stored once with a_id < b_id; created only by accept_friend_request, never by a direct client insert.
friend_requests
Pending requests keyed by (requester_id, addressee_id); a friendship is created only when the addressee accepts.
entry-photos (Storage bucket)
Public Storage bucket holding entry photos; writes are scoped to each user's own folder (first path segment must be their auth uid).

Backend

RLS is enabled on all seven tables: profiles and prompts are world-readable; entries are visible only to the author or a friend, and reactions and comments inherit that entry visibility via the entry_visible() helper; all writes are restricted to the owning user through auth.uid().
Friend-only visibility is enforced by the security-definer is_friend(a, b) and entry_visible(user, entry) SQL helpers used inside the entries, reactions, and comments select policies.
SECURITY DEFINER RPC handle_new_user() runs on the on_auth_user_created trigger on auth.users to auto-create a profile and resolve username collisions on signup.
Friendships are never inserted directly by clients: send_friend_request() and accept_friend_request() (SECURITY DEFINER) implement a request-then-mutual-accept flow, so nobody can self-grant a friendship or read another member's friends-only entries.
ensure_today_prompt(text) (SECURITY DEFINER) computes today's date server-side and idempotently creates the one shared prompt row for the day, so a client can't backdate or forge the prompt; there is no client insert policy on prompts.
After-insert and after-delete triggers on entries, reactions, and comments maintain denormalized counters (entry_count on profiles and prompts, reaction_total and comment_count on entries) and call recompute_streak() so the feed never aggregates at read time.
A before-update profiles_lock_counters() trigger forces the counter/streak columns back to their stored values for client (authenticated/anon) updates, so a member can edit display_name/username/bio/avatar_url but can never forge their entry count or streaks.
All seven tables (profiles, prompts, entries, reactions, comments, friendships, friend_requests) are added to the supabase_realtime publication for live feed/reaction/comment/request updates.
Photos live in a public 'entry-photos' Storage bucket with owner-scoped insert/update/delete policies (the first folder segment must equal the user's auth uid). No Edge Functions are used.