5 ms·

I tried to use this for a recent project but struggled with performance issues on Android. Not recommended at this time for production.

by kgc 13y ago

reedlaw 13y ago
Could you elaborate? It would seem performance issues would be tied to whatever Angular code is being written. Or are there UI issues?
- yesimahuman 13y ago
  Initially, we focused on iOS only just to get the alpha out in November. Turns out demand for Android was huge, but we were doing things that worked well on iOS (like box-shadow) and certain animations, but hurt Android performance on sub 4.4 devices. We've since built a system to gracefully fall back to less intensive operations on older Androids, and we have made a good amount of progress on Android performance over the last month (still more work to do as always). As many hybrid app developers will tell you, older Androids are like dealing with IE 6 when it comes to web. So we hope our work means a lot less for you.
  - vladgur 13y ago
    Define older -- 4.1.x and later represent more than 50% of devices out there: http://developer.android.com/about/dashboards/index.html http://developer.android.com/about/dashboards/index.html I agree with you on box-shadows -- its a big no-no in the android-land. There are some things however android chrome does better than mobile safari, batching browser repaints for instance. If you focus on CSS-driven animations/interactions for your ui, you should be able to reduce the performance issues on android though.
yesimahuman 13y ago
Thanks, Android performance is something we've been working hard on, and have made a good amount of progress with recently (especially on newer devices). Unfortunately, it's still lagging behind recent iOS devices. Making Android better is one thing this money will go towards :)
nicklovescode 13y ago
I used it in production for an application that is in the App Store right now(ChefSteps). It was a pleasure. It doesn't quite feel completely native yet, but it's close.

I tried to use this for a recent project but struggled with performance issues on Android. Not recommended at this time for production.

by kgc 13y ago

I tried to use this for a recent project but struggled with performance issues on Android. Not recommended at this time for production.

reedlaw 13y ago

Could you elaborate? It would seem performance issues would be tied to whatever Angular code is being written. Or are there UI issues?

yesimahuman 13y ago
Initially, we focused on iOS only just to get the alpha out in November. Turns out demand for Android was huge, but we were doing things that worked well on iOS (like box-shadow) and certain animations, but hurt Android performance on sub 4.4 devices. We've since built a system to gracefully fall back to less intensive operations on older Androids, and we have made a good amount of progress on Android performance over the last month (still more work to do as always). As many hybrid app developers will tell you, older Androids are like dealing with IE 6 when it comes to web. So we hope our work means a lot less for you.
- vladgur 13y ago
  Define older -- 4.1.x and later represent more than 50% of devices out there: http://developer.android.com/about/dashboards/index.html http://developer.android.com/about/dashboards/index.html I agree with you on box-shadows -- its a big no-no in the android-land. There are some things however android chrome does better than mobile safari, batching browser repaints for instance. If you focus on CSS-driven animations/interactions for your ui, you should be able to reduce the performance issues on android though.

yesimahuman 13y ago

Thanks, Android performance is something we've been working hard on, and have made a good amount of progress with recently (especially on newer devices). Unfortunately, it's still lagging behind recent iOS devices. Making Android better is one thing this money will go towards :)

nicklovescode 13y ago

I used it in production for an application that is in the App Store right now(ChefSteps). It was a pleasure. It doesn't quite feel completely native yet, but it's close.