Q: Importing existing screen
Hi,
So I have done almost the whole app design outside Krisspy manually using Figma (using UX Pilot for brainstorming UX which I then manually implement in my UI in Figma with the right typography/grid etc.). I am considering if Krisspy could replace UX Pilot in this flow and maybe partially Figma revisions.
But my big concern is how I take my existing UI design in Figma and continue iterating on them in Krisspy turning it into a prototype using Krisspy and AI instead of Figma. Can it take for instance a complete UI or UI kit and import it so I can tweak it using Krisspy.
And then the final step would be to be able to live export (not manual) my Krisspy screens to Github continuing editing and coding them using Visual Code Studio.
Would really appreciate if you can explain in detail how this workflow can look and what your plans are?

Sofiane_Krisspy
Mar 31, 2025A: Hey, sorry for the late reply — I thought I had already answered, especially since your questions are super relevant!
So for your first question: yes, absolutely — Krisspy can fully replace UX Pilot, and we can create complete workflows for apps that can then be continued directly within Krisspy. With our no-code capabilities, Krisspy is gradually evolving into something closer to Framer, allowing you to iterate and modify high-fidelity screens very quickly.
Figma import is being rolled out this week, and you’ll be able to import all your screens and convert them back into code. The only limitation (compared to full app creation in Krisspy) is that you'll need to manually link screens using the dedicated buttons in the interface.
As for code export — the React/Next/Vite export module has already been released in beta. It's an evolving solution, and you can already retrieve the full project. We don't yet support live GitHub sync, but the project can be run directly in a web container, or you can download a ZIP and continue working in Cursor.
Best
Would love to hear the answer too.
Hey George, I made an answer :)