Working on the next big step for PullPage: a real Next.js export
Right now, PullPage lets you export a snapshot of your Framer website and host it anywhere.
But I want to take it further.
I’m currently working on a Next.js/React export that gives developers fully editable code after exporting — so they can customize, extend, and maintain their website without being dependent on Framer anymore.
Build in Framer. Ship anywhere. And keep building from there.
It’s a very challenging feature to get right. Exporting something is one thing. Exporting clean, reliable, developer-friendly code is another.
For PullPage, a clean export is everything. I don’t want to ship code that technically works but becomes painful to maintain.
Still a lot to solve, but this could be a major step toward giving Framer users and developers true ownership of what they build.
This is a strong direction because the real pain is not just exporting a Framer site.
It is what happens after export.
A lot of tools can promise “export your site,” but developers will judge PullPage on whether the code is clean enough to actually own, edit, and maintain without feeling like they inherited a messy build artifact.
So I’d probably position the Next.js export less as a feature and more as a trust promise:
“Build visually in Framer, then own clean React code you can actually maintain.”
That speaks to the real buyer: Framer users who like the design speed, but do not want long-term platform lock-in.
The launch angle should probably focus on before/after examples too. Show one Framer page, the exported Next.js structure, and what a developer can safely change after export. That will create more trust than a broad “ship anywhere” message.
Happy to put a tighter version in writing if useful. There’s a clear positioning and launch path here around Framer lock-in, code quality, and developer trust.
Thank you for your reply, Aryan — I absolutely love your feedback! I'm currently stuck on the Framer API part and still need to figure it out. The first results via the public URL look promising, and I'm trying to improve the quality so that I can export it directly from the Framer project via the API.
That makes sense.
For PullPage, I’d separate the technical proof from the launch message. First get one clean export demo working. Then the whole positioning should probably be built around developer trust: Framer in, clean maintainable code out.
Drop your email and I’ll send over a tighter version of the launch angle. It’ll be easier to make useful in writing than turning this thread into a long breakdown.