Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It might work "best" on mobile devices, but I'm afraid that "best" is still pretty awful. In Chrome on a Moto G the frontpage gets maybe 5fps when scrolling. And not even consistently, but with seemingly random intervals between refreshes. The effect is physically nauseating, a bit like bad VR. On the same phone with Firefox it's even worse. The touch response is just so badly off that I can't even come up with a mental model of what's happening.

I'm sure you guys are proud of launching, and receiving criticism is never fun. But honestly there's no way this thing is usable at all on a midrange Android phone. If you as a company think otherwise, there must be some kind of collective self-delusion going on that you need to work out.

(If instead you had to launch now for some reason, even if you knew that the system isn't really production quality yet on most platforms... Well, too bad. But maybe you could benefit from stating up front on the page the environments where you expect it to work well, before all the launch goodwill is squandered by people not viewing the page on exactly the right platform.)



Thanks for the feedback. Out of curiosity, what version of Android are you running on the Moto G?


4.4.2 (the normal Motorola version, which is very close to stock Android). Chrome 34.


Out of curiosity, how did the demos perform on that device?

We'll work on making the demos available at standalone URLs (instead of iframed on our site). In the meantime, if you haven't tried them and want to, you can:

1) download the starter pack

2) go to the demos folder

3) open a webserver in each folder that serves the app.html as the index (just occurred to me that we should switch app.html with the iframed index.html for this very reason).

4) then open each demo on your phone over the local network.




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

Search: