Does anyone know if the elements are really native elements? Ie, they aren't some rendered html junk?<p>I may have to try this out, depending on how simple it is. I don't think it would fit for us at work, but if it's simple then it may fit nicely for my home projects. I've got lots of things i want to interact with via a phone app. If this means i can get a fast iteration cycle on little one-off (turn the lights on style) phone apps, then awesome!
I'm super excited about this. I've been waiting on an Android release since I saw this the first time, can't wait to apply this to some of my side projects
It looks decent and also seems like highly influenced by backend driven ui approach.[1]<p><a href="https://www.youtube.com/watch?v=ypk-72mhYBk" rel="nofollow">https://www.youtube.com/watch?v=ypk-72mhYBk</a>
it's nice but I tried it (via jason app) on my Moto G (2nd gen) and it's doing a lot of loading compared to the iOS version (tested on iPhone 5s)
It's not just "json".<p>It's a templating language, and a scripting language serialized down to a json. Of course any real app has to have some interactivity, and some state, and work with that state, push it to a server, maybe pull it from a server. Way to cumbersome to do it here.<p>This would probably be the "static site" equivalent in native land, but already with exponent/react/weex you have a much easier time setting things up.<p>At best, this can be called a good experiment.