My first thought was hybrid mobile apps built with WebViews. I’d be interested to see how those “feel” using something like LiveView.
mikemccall
dgmcguire
the main thing I want to take adv. of with texas is unpolys pre-fetch ability…since texas already can easily keep all the data up to date in real-time it could easily send a full rendering up so that link clicks would be instant with fully rendered html just being dropped in place - so yeah that would actually be faster to show usable pages than basically every front-end framework solution I’ve seen
0
peerreynders
When it comes to web interfaces I don’t expect the majority of IoT devices to have anything more sophisticated than your run-of-the-mill router administration interface as it could be cobbled together with something like apache-asp. Putting SVG/D3.js into the mix makes sense to boost the information visualization capabilities a bit.
By and large, I’d expect IoT devices to
- expose data and diagnostics in two formats: human readable HTML+ and machine-readable JSON/XML
- provide some interactivity for the purpose of device configuration
I would not expect them to
- burn lots of electical power, CPU cycles and bandwidth by providing continuous rendering support for a client app OR by serving some unnecessarily bloated JS SPA.
Anything requiring the “massaging of data” I would expect to be shipped off to some (data centre based) integration service.
0
AstonJ
I think that’s really interesting and I’d love to see what they’d be like too. I’m guessing it could be pretty awesome 
0
blatyo
Conduit Core Team
Do you mean Nerves device as the server or the client? As the server, I think it would work mostly fine as long as you’re on the right network. For the client, I can think of a lot of cases where it’s not a good idea. Some IoT devices are necessarily mostly/always offline. Those types of devices need the brains to be local.
1
chrismccord
Creator of Phoenix
Phoenix can run on the device itself, and I think a lot of the nerves folks are using Phoenix + headless chromium UI to power a lot of GUI interfaces, so in this case LiveView would be great even for offline usecases.
2
blatyo
Conduit Core Team
I meant, if the nerves device were the client. But, thinking about it, that doesn’t make much sense.
1
triskweline
This discussion focuses a lot on Turbolinks’ promise to load pages faster. And indeed with the performance of Elixir and Phoenix this is much less of an issue than with slower languages.
However, server-side apps also have the issue that all transient state (scroll positions, unsaved form values, etc.) is lost with every click:
Unpoly addresses this by only using the changed fragments of a server response. This solves most problems with transient state being destroyed:
We’ve found that in many apps this is enough to not need technology with more moving parts, such as SPA frameworks or web socket connections with persistent server-side UI state.
Here is an example app that illustrates this:
- We're breaking up with JavaScript frontends (classic server-side app)
- We're breaking up with JavaScript frontends (server-side app with Unpoly)
obsidienne
Hi,
My 2 cents, my webapp/website uses pjax-api. It’s like turbolinks but with the capacity to selectively update certain part.
I use it to maintain an audio stream and/or a YouTube video during navigation.
I configure pjax-api to replace only the main tag. No need for SPA.
It’s a good usecase for liveview. .
gregjohnson
Hi, For a comparison with where LiveView looks like it might be heading, in the Java world, Apache Wicket is a highly successful open source, component oriented, serverside web application framework that’s been doing server side since 2004 and with many thousands of production websites (being one of the few survivors of the Java serverside web framework wars of the mid 2000’s).
It successfully handles the impedance mismatch between the stateless nature of HTTP and the need to handle complex state without the usual MVC world of requests, routes, controllers, views etc.
Obviously it’s not as sophisticated as LiveView promises to be, however it’s a very successful model well worth looking at for lessons.
Regards …