Thanks for the clarification. I think the point of confusion for me was around the word "endpoint". As a web developer, I'm so used to thinking of the phone as the "endpoint" that the notion of the phone as the app server threw me a little.
One other concern I have is input lag. You mention gaming, which can require some pretty precise input timing. Have you run into any issues around that? Or are modern wifi network generally Good Enough that lag isn't a problem?
I only had enough time to whip up the quick demo here. The responsiveness is pretty tight as far as latency goes - it "feels" like the photo on screen moves in tandem with the one under my fingers. No perceptible lag.
I wanted to try out some more interesting demos. One idea I had was to run the HexGL racing game (http://hexgl.bkcore.com/) on the endpoint, and then have the app on the phone interpret the gyro as steering and send it over to the endpoint.
However, I found that WebGL on the pi is slooooow, for both Chrome and Firefox. I don't think this is a raw power issue so much as using desktop browsers on a mobile device, where the browsers haven't been compiled with driver support for the graphics chipset (the Pi can run Minecraft just fine, so it should be able to handle a simple racing game).
My educated guess (from just the photo-viewing demo) is that the latency is good enough to support responsive gaming input.
Comments
Thanks for the clarification. I think the point of confusion for me was around the word "endpoint". As a web developer, I'm so used to thinking of the phone as the "endpoint" that the notion of the phone as the app server threw me a little.
One other concern I have is input lag. You mention gaming, which can require some pretty precise input timing. Have you run into any issues around that? Or are modern wifi network generally Good Enough that lag isn't a problem?
I only had enough time to whip up the quick demo here. The responsiveness is pretty tight as far as latency goes - it "feels" like the photo on screen moves in tandem with the one under my fingers. No perceptible lag.
I wanted to try out some more interesting demos. One idea I had was to run the HexGL racing game (http://hexgl.bkcore.com/) on the endpoint, and then have the app on the phone interpret the gyro as steering and send it over to the endpoint.
However, I found that WebGL on the pi is slooooow, for both Chrome and Firefox. I don't think this is a raw power issue so much as using desktop browsers on a mobile device, where the browsers haven't been compiled with driver support for the graphics chipset (the Pi can run Minecraft just fine, so it should be able to handle a simple racing game).
My educated guess (from just the photo-viewing demo) is that the latency is good enough to support responsive gaming input.