Remix

Make your own version of DaGold Messenger

Get an exact, working copy in your account, then change anything with chat.

Original by Kelly Woodcastle

What would you change?

Start free with 40 credits. No card needed.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.

Build a complete, real messaging application called DaGold Messenger. It must work on Android phones and desktop browsers. This is a real application, not a static demo.

1. DESIGN AND BRANDING

Create a beautiful, premium, modern messaging app using these colors:

- Primary wine red: #722F37
- Deep wine: #4A1820
- Burgundy accent: #8B2635
- Soft blush: #F8EEF0
- White: #FFFFFF
- Background: #FCFAFA
- Main text: #292326

Use wine red for buttons, navigation, selected tabs, icons, and important actions. Use white backgrounds, soft blush highlights, rounded cards, elegant typography, and subtle shadows.

Create a simple wine-red and white DG logo with the name DaGold Messenger. Make the interface responsive and optimized for Samsung phones and other Android devices.

2. REGISTRATION AND LOGIN

Implement real authentication using Supabase Auth or another supported authentication provider.

Users must be able to:

- Register with email and password.
- Choose a unique username and display name.
- Verify their email.
- Log in and log out.
- Recover forgotten passwords.
- Maintain secure login sessions.
- Delete their accounts.

Never store passwords in plain text. Do not use fake authentication.

3. USER PROFILES

Each user should have a unique username, display name, profile picture, optional bio, online status, and last-active time when available.

Allow users to upload, change, and remove their profile pictures.

Use secure file storage and appropriate permissions.

4. SEARCH FOR FRIENDS

Create a functional search feature that searches real registered users by username.

Display matching usernames and profile pictures. Allow users to open profiles and start private conversations.

Never expose email addresses in public search results.

5. REAL-TIME PRIVATE CHAT

Implement genuine one-to-one messaging.

Users must be able to:

- Send and receive text messages in real time.
- View previous conversations.
- See timestamps and unread-message counts.
- View delivery and read status when supported.
- Receive messages without refreshing the page.

Use wine-red bubbles with white text for sent messages and white or soft-blush bubbles with dark text for received messages.

Store messages in a persistent database. Only authorized participants can access their conversations.

6. PICTURE SHARING

Allow users to select pictures from their phone galleries, preview them, and send them privately.

Display received pictures inside the conversation. Include upload progress, error handling, supported image formats, and reasonable file-size limits.

Store pictures securely and prevent unauthorized access.

7. VOICE NOTES

Implement real voice-note recording and playback.

Users must be able to:

- Record audio using their phone microphone.
- Start and stop recordings.
- Preview or cancel recordings.
- Send voice notes in private chats.
- Play and pause received recordings.
- See the recording duration, sender, and timestamp.

Request microphone permission when necessary. Use audio formats supported by Android browsers.

Store audio files securely. The recording, uploading, sending, and playback functions must actually work.

8. REAL INTERNET VOICE CALLS

Implement real one-to-one audio calls using WebRTC.

Include:

- Start-call button.
- Incoming-call screen.
- Accept and reject buttons.
- Microphone mute and unmute.
- Active-call timer.
- End-call button.
- Missed-call history.
- Connection error handling.

Implement secure real-time signaling between authorized participants. Configure STUN support and document TURN server requirements for networks that need them.

Request microphone permission before calling. Use wine-red call controls on a clean white screen.

Never simulate successful calls or pretend a connection exists when it has failed.

9. MAIN DASHBOARD

Create a polished dashboard showing recent conversations, profile pictures, usernames, last messages, timestamps, unread-message badges, and online indicators when available.

Include a working conversation search bar.

Create mobile bottom navigation for Chats, Search, Calls, and Profile.

Every navigation item must work. Include helpful empty states when no conversations exist.

10. CALL HISTORY

Display incoming, outgoing, and missed calls with contact pictures, usernames, timestamps, and call duration when available.

Allow users to call contacts again from this screen.

Store genuine call records, not invented events.

11. BACKEND AND DATABASE

Use Supabase if supported by the platform.

Implement real authentication, PostgreSQL database storage, real-time messaging, and secure file storage.

Create the necessary tables for:

- User profiles.
- Conversations.
- Conversation participants.
- Messages.
- Picture attachments.
- Voice-note attachments.
- Voice-call records.

Configure database relationships, row-level security, and appropriate access policies.

Keep secret keys and administrative credentials out of frontend code. Use environment variables for sensitive configuration.

If an external account or configuration is required, explain the setup steps.

Prefer free-tier services. Do not purchase subscriptions, upgrade plans, or incur paid charges without my permission.

12. REQUIRED SCREENS

Build:

1. Welcome page.
2. Sign-up and login.
3. Password recovery.
4. Chat dashboard.
5. Username search.
6. User profiles.
7. Private conversations.
8. Picture-sharing interface.
9. Voice-note recorder and player.
10. Incoming-call screen.
11. Active-call screen.
12. Call history.
13. Account settings.

Keep the wine-red and white design consistent across every screen.

13. SECURITY AND DEPLOYMENT

Protect private conversations and uploaded files. Validate user input and prevent unauthorized access.

Do not claim end-to-end encryption unless it has genuinely been implemented.

Make the app responsive and prepare it for deployment to a public URL so friends can use it from different phones.

Test registration, login, username search, real-time messaging, picture sharing, voice notes, microphone permissions, and voice calls.

Do not mark unimplemented features as complete. Clearly identify any remaining setup requirements.

FINAL INSTRUCTION

Build DaGold Messenger as a real, usable application with a wine-red and white design.

Implement the interface and backend, starting with registration, username search, and private messaging. Then implement picture sharing, voice notes, and real WebRTC voice calls.

Use genuine accounts, persistent storage, and real communication. Do not use fake users, sample messages presented as real, or nonfunctional buttons.

Prioritize mobile usability, privacy, reliability, and free services wherever possible.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.