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.
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.
Perhaps I was too negative in my tone in my parent message. My point is that you can make anything a json. For example
site = {html: "..", js: "..", css: ".."}
The above is technically a json, but it would be incorrect to refer to above as "build websites with json". It's markup, styling and scripts simply serialized to a json. So rather than a framework, it becomes just a transport layer.
Hope that clarifies why I do not think of Jasonette as "json" defined native app. "Create your own native Android app with nothing but JSON." is incorrect, as you're actually using scripting etc in there.
Does anyone know if the elements are really native elements? Ie, they aren't some rendered html junk?
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
10 comments
[ 2.8 ms ] story [ 24.6 ms ] threadIt'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.
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.
At best, this can be called a good experiment.
site = {html: "..", js: "..", css: ".."}
The above is technically a json, but it would be incorrect to refer to above as "build websites with json". It's markup, styling and scripts simply serialized to a json. So rather than a framework, it becomes just a transport layer.
Hope that clarifies why I do not think of Jasonette as "json" defined native app. "Create your own native Android app with nothing but JSON." is incorrect, as you're actually using scripting etc in there.
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!
Integration is pretty easy I'm using the plug-in system of Jasonette to hook into Azure APNS and their Mobile App Tables thingy.
https://www.youtube.com/watch?v=ypk-72mhYBk