Hey Adrien,
As the PM in charge of UI features on Forge, I can’t answer all of your questions but just wanted to touch on your points about UI:
We have to develop on Connect right now because customers are forced to move to the cloud now, but in 3 months we’ll have competition from the pure-Forge apps. Are we going to throw away the code of our current UI in 6 months, because we are pushed to migrate to Forge?
We just launched custom UI, which lets you use arbitrary HTML/CSS/JS on Forge. As long as your frontend is static, you should be able to move it over with almost zero code rewriting (if not now, very soon, since we’re rushing to bridge the gaps between Connect and Forge). If you were pushed to migrate to Forge—which would only happen if there wasn’t going to be any functionality loss and significant security advantages—you wouldn’t have to throw away your current code.
Also, since Forge and UI Kit are domain-specific DSLs, programmers can’t reuse their skills in other companies, so my current programmers will start leaving if we are on pure-Forge.
I see the point you’re making.
- You don’t have to use UI kit to be on Forge, custom UI should allow developers with almost any web skillset to work at your company (unless they know PHP
). - UI kit has a very similar API to React Hooks. I’m not fully convinced you’d be locking people into something with little applicability elsewhere—but I get your point. We’ve been looking at ways to make UI kit less domain-specific but don’t have anything to share right now.