Hacker News new | past | comments | ask | show | jobs | submit login

And there's tons of background processing hooks for making that happen. They are detached from the UI portion of the API though.

I can't think of work that needs to be performed that requires a GUI to constantly be loaded, but doesn't require that the GUI be in the foreground.




I do have 5 tablets in my home, held with magnets against the walls, which do nothing else but have a custom app running which displays a full-screen WebView.

It shows stuff like weather, clock, calendar, land-line phone calls and has buttons for light scenes.

I used to use Chrome for this, but I always had to manually maximize the page, and hosting it in a custom app has additional benefits, like loading and maximizing the page as soon as the device boots, and offering a JavaScript interface so that the page can interact with Java functionality. It's much better that just hosting the page in Chrome.

Each time Chrome gets updated, the app gets killed. And even though the app has set up an alarm which makes Android call into the app every minute to ensure it is running, for some reason this doesn't bring up the UI (probably something which I need to debug).

But I know that if this app were running on Linux directly, in some Python Qt app with a Qt WebView, it would never get killed, as it has plenty of resources available.

I've also considered integrating Mozilla's rendering engine into the app, but decided not to, I can't remember why, but there were some drawbacks in doing so.

It would be hard to imagine using such an app in an industrial setting, where the app would need to be visible all the time, displaying gauges and stuff like that. The hardware could do that, with a proper OS.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: