Depends on the implementation. With a two-phased approach, the UI can be fetched remotely ahead of time in the background and stored on disk before the user needs to see it.
This is a solution for native iOS and Android apps. Rendering HTML within a native app has a ton of tradeoffs. SDUI is about bringing some of the benefits of HTML websites to native apps without compromising on platform…
A CMS (e.g. Contentful) provides the content/data. SDUI is about using that same technique for the layout of the user interface itself.
Embedding a web view has a ton of tradeoffs. A good implementation of SDUI will support all the native platform features like accessibility, dark mode, localization. Not to mention the user experience is much more…
Thank you for this feedback! I'm gonna bump the priority of the placeholder feature in our roadmap. I think the use case you're describing is a very common one. Judo experiences integrate themselves seamlessly into your…
Ya right now sharing to your iPhone with Airdrop is a good workflow. You can also send experiences via iMessage and it will open directly in iMessage because we implemented the QuickLook extension. Also, we are…
Great feedback, this is really helping us understand how to improve our messaging. The blog section in your app is a great use case.
We are planning full Mac support for Mac apps that are built with SwiftUI. But if your Mac app is built with Catalyst it may very well work today...
Good feedback, thanks for sharing. I have passed these comments on to Kevin the product specialist in the videos. We have a new Learning Center section of the website launching soon that will organize all the content…
Agreed. We have work to do!
Right now we support iOS and Android. But we have Mac support on the roadmap.
Ya you got it. SwiftUI wasn't viable before Big Sur.
It's both a no-code tool for building native mobile interfaces AND a platform for hosting/serving them remotely (i.e. server-driven UI). It doesn't make sense to use this for your entire app but it's an invaluable tool…
There will be self-serve pricing coming very soon. In the meantime the product is free to use. Feel free to reach out via our contact form if you want to discuss pricing sooner. https://try.judo.app/contact-us/
Exactly. We love SwiftUI's layout system. It has a learning curve but once you "get it" it feels so intuitive to build naturally responsive layouts. Since our SDK is rendering native SwiftUI we decided the best…
Good feedback. We're still ironing out the onboarding UX. In the meantime, this getting started page should help: https://try.judo.app/getting-started/
Judo is meant to integrate into your existing iOS and Android app. It's not an "app builder" platform. Instead, Judo facilitates server-driven UI for parts of your app where it makes sense. Typically areas that are…
Depends on the implementation. With a two-phased approach, the UI can be fetched remotely ahead of time in the background and stored on disk before the user needs to see it.
This is a solution for native iOS and Android apps. Rendering HTML within a native app has a ton of tradeoffs. SDUI is about bringing some of the benefits of HTML websites to native apps without compromising on platform…
A CMS (e.g. Contentful) provides the content/data. SDUI is about using that same technique for the layout of the user interface itself.
Embedding a web view has a ton of tradeoffs. A good implementation of SDUI will support all the native platform features like accessibility, dark mode, localization. Not to mention the user experience is much more…
Thank you for this feedback! I'm gonna bump the priority of the placeholder feature in our roadmap. I think the use case you're describing is a very common one. Judo experiences integrate themselves seamlessly into your…
Ya right now sharing to your iPhone with Airdrop is a good workflow. You can also send experiences via iMessage and it will open directly in iMessage because we implemented the QuickLook extension. Also, we are…
Great feedback, this is really helping us understand how to improve our messaging. The blog section in your app is a great use case.
We are planning full Mac support for Mac apps that are built with SwiftUI. But if your Mac app is built with Catalyst it may very well work today...
Good feedback, thanks for sharing. I have passed these comments on to Kevin the product specialist in the videos. We have a new Learning Center section of the website launching soon that will organize all the content…
Agreed. We have work to do!
Right now we support iOS and Android. But we have Mac support on the roadmap.
Ya you got it. SwiftUI wasn't viable before Big Sur.
It's both a no-code tool for building native mobile interfaces AND a platform for hosting/serving them remotely (i.e. server-driven UI). It doesn't make sense to use this for your entire app but it's an invaluable tool…
There will be self-serve pricing coming very soon. In the meantime the product is free to use. Feel free to reach out via our contact form if you want to discuss pricing sooner. https://try.judo.app/contact-us/
Exactly. We love SwiftUI's layout system. It has a learning curve but once you "get it" it feels so intuitive to build naturally responsive layouts. Since our SDK is rendering native SwiftUI we decided the best…
Good feedback. We're still ironing out the onboarding UX. In the meantime, this getting started page should help: https://try.judo.app/getting-started/
Judo is meant to integrate into your existing iOS and Android app. It's not an "app builder" platform. Instead, Judo facilitates server-driven UI for parts of your app where it makes sense. Typically areas that are…