LabVIEW mobile device user interface using web browser

[vitoi]

This idea is similar to two other ideas:

1) http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Support-for-HTML5-and-SVG-in-Web-Publishing-Tool/idi-p...

2) http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Remote-Access-to-LabVIEW-using-HTML5/idi-p/1944781 ,

However, this idea has the following unique aspects/extensions:

1) In the past, it appears that the decision needed to be made between a Native App (like Data Dashboard) or a Web App. However, I believe both should be developed by NI. See http://www.ericbrynsvold.com/2011/11/native-vs-web-app/ and http://www.webmonkey.com/2010/08/how-do-native-apps-and-web-apps-compare for more details and an examination of the pros and cons. Facebook has both a native app and a mobile app and the user interface looks the same! So, the important thing is, it’s not one or the other, with both having their place.

2) Don’t develop the LabVIEW web app fully and then release it. Follow the path taken by the Data Dashboard for LabVIEW and release bits at time. This way we get something to use relatively quickly. Just simple numeric controls and indicators and Boolean controls and indicators would do to start with.

3) Put as much development effort into the web app as is currently going into the native app (Data Dashboard for LabVIEW).

4) The web browser user interface should reflect the contents of a VI. Also, multiple VIs / sub-VIs can be addressed. This last part is important since different devices may need different interfaces. For instance, for my upcoming home automation project, the user interface for the bedroom would be different to that for the home theatre.

Although Native Apps like Data Dashboard give a rich user experience, the effort required to handle multiple platforms can become onerous, as detailed in https://forums.ni.com/t5/Smartphones-Tablets-and-Mobile/Troubleshooting-and-Support-Data-Dashboard-f... . The Web App does not have to have the performance of the Native App. What is lost in performance (and I think this is not a big issue) it gains in universality.

I believe the need for both LabVIEW remote access using native and web apps, the concept of releasing early and releasing often and putting the same level of effort as the native app are the essence of this idea.

It important that the web app be able to use a standard web browser without any plug in. This way any mobile device can be targeted.

Wouldn’t it be great to use any web browser to provide a great remote user interface for LabVIEW?

[triviper]

Is there a way to vote FOR this? Great idea.

[elset191]

---

@triviper wrote:

Is there a way to vote FOR this? Great idea.

---

Hit the yellow kudos button in the top left.

[Igor_Titov]

Solved with WebPager (https://www.ni.com/en/support/downloads/tools-network/download.webpager.html, https://labicom.net/labdeveloper/WebPager/webpager_demos.html).

[vitoi]

Thanks for the info Igor. I'll have to look into it on day.

There does not appear to be an evaluation version to check it out. Performance would be an important measure before committing to using it and purchasing.

Very odd pricing. The cost looks like $150/month (assuming one does not want to commit to a year's service). Presumably this is per server. There are free solutions available, so WebPager would have to have some significant advantage to warrant the high ongoing cost. (I like to buy my products, not rent/lease them.)

This idea was to include the ability for LabVIEW to have a standard browser be able to be used as a front panel. That is, it would be a feature of LabVIEW (at no extra cost). WebPager does not fulfill the idea's requirement since there is a (significant) cost component.

Still hoping NI include a standard browser interface. However, judging from the level of interest, it does not appear to be a priority with users. (How hard can it be to write VI's that serve HTML code to render the various indicators. Might just do it myself when needed. Or maybe write my home automation application in Java.)

[Igor_Titov]

There is an evaluation. Just register, install it and start using it. On the 'Account' tab there will be info on when it expires. And after this it's in paid mode, you don't have to install it separately.

The cost is much more flexible than for many other LabVIEW-related products. You can buy licenses by year/by month/by day/by minute, and they start from cents. So, you have a choice and you have to find out how often you'll be using it.

As to a native feature of LabVIEW - who told you that it will be of no extra cost?  Looking into the past at Web Publishing Tool and Web UI Builder, it's safe to predict that it will be more expensive than WebPager (if ever comes up).

[Igor_Titov]

Hi again:)

Now there is one-time fee for WebPager. And local network is supported, it should solve you problem...

[Darren]

Any idea that has received less than 7 kudos within 7 years after posting will be automatically declined.