campus-devcon-10-2014



campus-devcon-10-2014

1 0


campus-devcon-10-2014

Slides for Devcon Summit 2014

On Github padc / campus-devcon-10-2014

Android

Why you should go native

Tradeoffs

  • Every engineering decision is a tradeoff
  • Frameworks, tools, methodologies, platforms
  • Time, money, expertise; in no particular order

whoami

Evan Dale Aromin

  • coins.ph
  • Philippine Android Developers Community
  • Android, Python, JS
  • @avendael

Performance is not everything

  • Team expertise
  • Time available
  • Resources available
  • Most devices are resource constrained
  • Tooling
  • The web will catch up?
  • I would wager that you could learn native faster than the web catching up

The network is unreliable

  • Obviously, m.yourapp.com is largely affected
  • Both native and mobile web apps can somehow compensate

Look and feel

  • Mobile web apps can be made to look like native apps
  • Native platforms change look and feel on a whim
  • Design guidelines easier to implement in native

Best tool for the job

  • Take advantage of new APIs early
  • Take advantage of new hardware features early
  • Keeps on getting better per release
  • Dedicated team for Android Tooling (ADT, Android Studio, etc.)
  • Background services always require native knowledge

Huge market

Jobs

Community

  • Lots of resources on how to do things
  • Active stackoverflow community
  • Lots of open source libraries
  • DevBytes, developer.android.com

ymmv

Thanks!