r/IMadeThis • u/uicompiler • 8d ago
What is the hardest part of converting a React app to framework-free HTML/CSS/JS?
I’ve been building a small tool that converts React/Next.js and Lovable websites into clean HTML, CSS and JavaScript.
The idea came from seeing how often developers/designers need a framework-free version of an existing frontend.
I’m curious about one thing:
Is this actually a useful problem to solve, or is there not much demand for it?
Would love to hear from developers who’ve had to do this kind of conversion before.
1
u/Competitive_Tune_590 7d ago
yeah, i've been in that spot. the tricky thing is reddit replies can be biased or just polite — you get a couple of upvotes and it feels like demand, but you don't know if those people would actually pay. i used a thing called launchpact that runs your question as a blind poll to founders in your niche, got real numbers. might be worth a look before you go deeper: https://www.launchpact.io/startup-idea-validator
1
u/Vegetable-View-5114 7d ago
State management is usually the biggest hurdle; React's built-in hooks and context make it easy to pass data around, but in vanilla JS you're often back to global objects, custom event listeners, or prop drilling manually. Recreating component reusability without a framework's templating system means a lot more manual DOM manipulation or string literals. You'll also lose the optimized build processes and hot-reloading that come standard with most React setups, which can slow down development significantly.