For Valentine's day I used @Replit to make an app (PWA) that lets me and my partner "hug" via notifications, and has an exploding heart when we're both touching a button at the same time.
What I'm stoked on:
I was able to get a prototype in minutes even though it had a lot of flaws. It took me a couple of sessions over a few days to build an app that kind of works. This was pretty mind-blowing, as my coding ability is fairly rudimentary (background in data science and I've done some basic javascript but never built a standalone app).
Using @Wispr Flow sped things up and also was impressive - It's cool to see the little touches that Wispr has implemented to improve dictation, and I'm just impressed by the speed and fluidity of using it on desktop. As a side note, using Wispr has made me increasingly frustrated at how poor iOS's built-in voice dictation is.
What I'm frustrated by:
I had to restart building the app a couple times because when I would try to get it to fix certain things, it would create more problems. It felt like working with a very fast but extremely inexperienced developer who has no sense of when they're off on a dead-end in the maze.
I haven't developed an intuition on when to use agent and when to use assistant. Replit shows how the agent is more expensive than the assistant, which stressed me out a bit. Although I realized I never hit the threshold where it started charging me more than my normal subscription. So I think it was just a psychological thing.
It had repeated errors around web socket connections and dealing with notifications on iOS. I had to get deeper and deeper into these myself, and in one case, teach it how to do notifications properly on iOS. It turned out that Replit's information was outdated, and it thought that it is not possible to do native notifications with a PWA on iOS. So I had to actually get code from ChatGPT to teach it.
It was stressful to make a change knowing that I could break and was likely to break many other things, and I didn't know how to properly create a checkpoint that I could fall back to. It creates checkpoints all the time, but I couldn't figure out how to name a checkpoint or save it in a way that was easily recoverable.
Because it takes some time for Replit to compile, I've found myself doing other things like work, little tasks, or even watching a TV show while waiting for Replit. But then I had to keep checking because it wouldn't send me a notification. I wonder if there's a way to send notifications?
Help me make my workflow better! What am I doing wrong / what could I be doing that I'm not doing?
Congrats launch! What’s the most surprising project you’ve seen built with just prompts, and did it challenge how you thought people might use Replit?
@amjad_masad @amasad @saaswarrior There should be a prompt library or template system that allows users to build and preview expected outputs before committing to full generation. Right now, it’s frustrating to wait 30 minutes for a design, only to realize the prompt wasn’t effective — and then have to start over again and again.
Love it. Excellent work!
PROCESIO
Congrats on the launch! 🚀 Lowering the barrier from idea to app is a huge win for creators. How do Replit’s Agent and Assistant handle code quality and security—especially for auto-generated projects? Also, are there collaborative features for teams to build and debug together in real time, and how does the platform support scaling from prototypes to production apps?
X-Design
Congrats on the launch! Excited to see how you build on this foundation in the coming months.