Nostr Web Client

nostr:npub1qtgmfq7jruka7l7q96gjlk4ar2ljjnsmca6l4l3atwldhyz7q5aqwnh07s nostr:npub1zxu639qym0esxnn7rzrt48wycmfhdu3e5yvzwx7ja3t84zyc2r8qz8cx2y nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424

Quick follow-up guys on the replit webapp I've been working on. Would love your thoughts...

As a 25yr UX Vet that worked with Devs daily, I started to question how 'real' this webapp was. Meaning how much can I actually trust the underlying security and maintainability of the code if I launch it and start to get 100's of users?

Should I view the Replit code as a quick proof of concept and then expect I'll need to hire a dev to actually build it 'properly', 'securely', etc.?

Basically, it doesn't seem real that I can code up this app in replit, launch it, build up a user base, and somehow it will be secure and maintainable when I don't really know the code behind it is correct...

Thanks!

Reply to this note

Please Login to reply.

Discussion

E 3w ago 💬 1

Seems like Cursor may be interesting...

Fabio Krauss 3w ago

I don't think you will throw it all out afterwards. It is still a good thing to keep and prototype on as you evolve.

The main drawback I see on replit: it skews you into using their infra. But that doesn't mean you can't hire a developer (or even cursor) to change that. One can develop on replit and commit code to GitHub, which makes you free to use cursor (and also replit) for evolving and making it more robust.

But that doesn't mean you'll throw it all out. It might just mean that your workflow switches to cursor and you work together with developers on the same repo.

A second drawback I see is that replit and cursor are both in one single repo. As your feature set grows it makes it harder for the models to be fully aware of your context. Here again might you may hit a point where you want to hire someone to help you restructure and architect the code. It is not incompatible with the cursor idea i shared above.

If I were in your place I would start by

1) dual development - replit and cursor - because it creates the foundation in GitHub for you to collab with a developer. You'll start using issues, actions etc. You'll gradually turn replit into one part of your dev cycle

2) start looking for a dev that could help you structure the code and architecture.

All in all you don't need to ditch replit completely but you can grow further than it's vanilla usage

E 3w ago

Thanks so much for the response nostr:nprofile1qqsq95d5s0fp7twl0lqzayf0m27340effcduwa06lc74h0kmjp0q2wspzpmhxue69uhkumewwd68ytnrwghszrnhwden5te0dehhxtnvdakz7qg7waehxw309ahx7um5wgkhqatz9emk2mrvdaexgetj9ehx2ap09j7atf Diving back in to three separate projects. I'm in that good phase where you wake up at 2:30am wanting to get started!!

Derek Ross 3w ago

Check out https://shakespeare.diy over Replit. Our platform is fully open source and allows for user choice and freedom. It's so much better than Replit in this regard.

That said, it depends on what you're building. Some things can be seen as production ready and others might need some clean up or enhancement when done. The latest models from Anthropic, such as Claude Opus 4.5 are so damn good. I mean damn good. You might be surprised with what it's able to build. I wouldn't call what it's able to do as PoC, again, depending on the complexity of the site.

E 3w ago

Thanks, as always nostr:nprofile1qqsr7acdvhf6we9fch94qwhpy0nza36e3tgrtkpku25ppuu80f69kfqppemhxue69uhkummn9ekx7mp0qyghwumn8ghj7mn0wd68ytnhd9hx2tcpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcmuvweu!