Bubble.io vs AI Coding (bolt.new, V0, Cursor AI, Replit, Claude AI)

Meta
30

I’ve been testing all manner of AI app building tools. Today for example I gave Replit and Lovable this prompt:

### **Prompt for AI Development of "Riot Events" Web App**
**Goal:**
Create a custom conferencing web app that allows users to host live events, including scheduling, RSVP management, live streaming integrations, and user account management.
### **1. General Structure and Functionality:**
**Public Pages:**
- **Landing Page:**
  - Minimalist design with black, white, and gray colors.
  - Centered header: "Riot Events."
  - Right corner of the header has a "Login" button that links to the login page.
- **Login Page:**
  - Simple form to allow users to log in to their accounts.
- **About Page:**
  - Brief description of "Riot Events" platform and its features.
**Private Pages (Logged-in Users):**
- **Dashboard Page:**
  - Left-hand side menu displaying a list of scheduled events.
  - Each event is displayed as a floating tile card, showing:
    - Event title in large font.
    - Scheduled time, including timezone and RSVP count.
    - A plus button if no events are scheduled, allowing users to create a new event.
  - Event card includes:
    - **Edit (pencil icon)** and **Delete (x icon)** buttons for modifying or removing events.
- **Logged-in Event Owner Page (for event creators):**
  - Clicking an event tile redirects to a dashboard showing a list of users who RSVP'd to their event.
  - The RSVP list should include user names, email addresses, and timestamps of their RSVP.
**Admin Page:**
- Admin Dashboard should:
  - Show all platform users and allow admins to delete users.
  - Have a menu toggle between viewing all users and viewing all scheduled events.
  - Allow admins to modify or delete any event or user’s details.
### **2. Event Management Pages:**
- **Schedule New Event Page:**
  - Form to collect:
    - Event Title.
    - Event Description (max 500 characters).
    - Event Time (hour, minute, and timezone dropdown).
    - Maximum RSVP count.
    - YouTube Livestream URL.
  - **Submit Button** to save the event and update the user dashboard with the new event.
  - Upon submission:
    - A unique 12-character URL slug should be generated.
    - The event should be linked to the logged-in user as the event owner.
- **Event Page:**
  - Publicly accessible page with:
    - Event Title.
    - Event Description.
    - Event Time.
    - RSVP Button that opens a modal.
  - **RSVP Modal** collects:
    - User’s name.
    - User’s email address.
    - Submit button to save RSVP information in the backend, associating it with the specific event.
### **3. User Account Settings:**
- **Account Settings Page:**
  - Logged-in users should be able to navigate to their **Account Settings** page from their dashboard or a user profile icon.
  - **Password Update:**
    - Include an option for users to update their password.
    - **Form to collect:**
      - Current password.
      - New password (with strength validation).
      - Confirmation of new password.
    - After submission, the password should be updated in the database securely.
### **4. Administration:**
- Create an admin user profile:
  - **Email:** test@test.com.
  - **Password:** 123456.
  - This user should have access to an "Admin Dashboard" and be able to manage all events and users.
### **5. Backend Requirements:**
- **User Profiles:**
  - Each user should have a profile that includes:
    - Email.
    - Password.
    - Date created.
    - Status (active or deleted).
- **Database:**
  - Use Supabase for managing user profiles, events, and RSVPs.
- **Event Data:**
  - Store all events, including their details (title, description, time, RSVP count, YouTube URL).
  - Each event should be associated with the user who created it (Event Owner).
  - Event data should be accessible through unique URL slugs for public access.
- **Live Streaming:**
  - Use the YouTube API to embed live event streams on the event page via an iFrame.
  • Lovable crashed after 3 minutes and would not continue regardless of what I prompted.
  • Replit partially built the app to spec (missed building an admin dashboard for example) and then it ran into a 400 error in the Event Creation modal and after 10 more prompts it crashed the whole app (It stopped loading ).

I’ve had success with these tools for “microapps” that have single purposes.
Has anyone being able to build something more complex? Would love to play with some examples (if you are ok sharing of course)

1 Like