I Built a Research Assistant That Converts Papers Into Podcasts, Slides Using v0, Grok AI + Supabase

In the spirit of vibe coding and building something useful without overthinking it, I recently created a lightweight AI-powered web app called ResearchAI Assistant. Doing a lot of my masters dissertation and having to deal with a ton of papers and research, I decided to vibe code something that will be helpful to me if built upon.

It helps researchers, students, and professionals transform complex academic papers into accessible content like slide decks, podcasts, summaries, and visuals—all in just a few clicks.

The front end for this project was already largely built out

👉

• 📊 Interactive Slides – Turn technical content into slide presentations with just a paste/upload.


• 🎙️ Podcast Scripts – Generate AI-narrated audio scripts from research papers.


• 📄 Executive Summaries – Extract key points into short, digestible formats for stakeholders.


• 
  

  📈 Visual Infographics – Create simplified visual content and diagrams.

  
  
  
  
  
  • 📤 Upload or Paste Research
    
  
  
  
  
  
  




• Supports PDF, DOC, DOCX, and TXT files (max 10MB).




• 
  
  

  Paste content directly for on-the-fly analysis.

  
  
  
  
  
  • 🔐 Secure Auth with Supabase
    
  
  
  
  
  
  




• Users must confirm their email before signing in.

🧠 Behind the Scenes

• 
  Frontend: Built with React and styled for a dark theme that’s sleek and professional.


• 
  Backend: Authentication and database powered by
  
  
  
  
  
  • ✅ Analysis Complete
    Shows estimated reading time, complexity, and key insights.
  
  
  
  
  
  
  
  
  
  • Dynamic Sign-Up page
  
  
  
  
  
  
  
  
  
  

  
  
  
  Final Thoughts
  

  
  
  

  This wasn’t about building a “perfect” product—it was about vibing with a useful idea and turning it into a live, testable prototype. If you're a student, researcher, or builder who loves experimenting with AI and interfaces, this is a fun project to explore.
  
  I should also add that I vibe wrote this article. I gathered all the data I need for the article, including screenshots, key points, and relevant links. I fed it into an LLM, and it came up with an article draft, which I went ahead to modify.
  
  The idea is that if I can vibe code an entire app, why can't I vibe write an article draft?

  
  
  

  Got feedback or feature ideas? Drop a comment!

  Vollständiger Original-Bericht

  Ausführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf dev.to.

  ↗ Original-Artikel auf dev.to lesen