4 ms·
This link might be useful to your team: http://en.wikipedia.org/wiki/Android_version_history http://en.wikipedia.org/wiki/Android_version_history Looks like Ki
by ChrisAntaki 12y ago
This link might be useful to your team: http://en.wikipedia.org/wiki/Android_version_history http://en.wikipedia.org/wiki/Android_version_history
Looks like KitKat has been out for 6 months. Just a heads up, the best Android devices are running KitKat, like the S4 & S5. I can confirm, the Famo.us scrolling & animations have issues on the S4.
That being said, your framework is amazing on iOS, and feels like a native app. I'm sure your team will have no problem with KitKat, if time is dedicated to it.
- malandrew 12y agoOh we're familiar with it and we spend time trying to get Android working well. It's been a more challenging platform because the performance of the underlying APIs on Chrome has been more erratic. FWIW, I made this versioning mistake because I'm one of the two people in the company who is the least familiar with Android versioning because I work on backend systems and tooling that we'll be releasing later this year. 90% of my time is spent in the terminal. Anyways, homepage clearly needs some a lot of love. In the meantime, do you mind trying the following instructions in this comment, https://news.ycombinator.com/item?id=7771330 https://news.ycombinator.com/item?id=7771330 , on your Android device to see how the demos perform?
- ChrisAntaki 12y agoHey Andrew, thanks for the clarification. I only had time to check out Albumatic, Rise, and PHQ4, on the Samsung S4. Albumatic was a bit laggy, Rise & PHQ4 were pretty great. Will have more feedback after the Hackathon.
- ChrisAntaki 12y agoPost Hackathon: Great framework. Really interested to see where it goes.
- malandrew 12y agoAwesome. Thanks for the feedback. We're working hard on pushing things forward and will fix the initial problems we've had.