I like this a lot. I'm currently thinking a lot about how to expose more control of our article content to our content team. They want to be able to build much more complex layouts, use more imagery, embed videos, control the information hierarchy, and even do basic interaction like buttons to go to show/hide different content.<p>We're all SwiftUI, so while creating each bit of this isn't a lot of work itself, we need to add it to our API, backend, CMS, editor, database, etc. The more control we can give them over all this the better.<p>That said, there are things where we (as an engineering team) still need some control. Device support, accessibility – I can see these are fully supported and can be previewed, that's great! A few things that look missing that it would be good to see:<p>- Design system/styles/etc – we have a set of styles, colours, typefaces, padding sizes, etc that we want to use and/or strongly encourage.<p>- Custom data. We'd like to be able to pass in details from the system, like who's logged in, name and other user properties that matter in our product.<p>- Custom components. We have things like a product card component that it would be great to be able to re-use here. How that would get its data though... not sure.<p>- Custom actions. I can see something about this in the app but not sure how it works. We would want to be able to link to places in the app, ideally with URLs, and have responsibility of presenting that UI handed back to the non-Judo part of the app.<p>I may be assuming a lot about the product here, maybe this isn't the direction you're thinking, but I'm generally excited by this and keen to see how it develops over time.