SEEKING WORK
Location:Greater ChicagoLand
Remote: Open to remote and relocation
Portfolio: http://shareme.github.com
Speciality: Android(native java)
Stacokoverflow Score: Top 10% Android(rated by other developers)
The name of the game in grabbing a piece of the M&A increase in 2016-2017 is an increasing MAU engine. On the Android Platform that means polished UI components integrated with Google Material Design showing a visible change in UI workflow to introduce new app features with new version of the app.
The problem is if you do new app features as UI changes(its the only way that makes sense as you have to integrate with app users perceptions and worldviews) you run into UI feature back port problems. And to be blunt honest the average android developer fails at knowing android suport internals well enough to get any UI feature back-ported correctly. But, if I pay attention to android support internals and back port the UI features correctly than the UI changes to highlight new app features becomes a breeze to implement and thus we get a potential an increasing MAUs engine(my library back ports the UI features correctly and gives a solid foundation for implmenting Material Design UI components without having to worry how to back port them and thus can focus on the UI visible changes that signal a new app feature).
Since that increasing MAUs engine is focusing on grabbing M&A and or IPO results for a start-up in the form of leveraging MAUs for MA& and or IPO it might be advantageous to begin an email conversation with me if your start-up is newly funded and seeking their first android developer.
The name of the game in grabbing a piece of the M&A increase in 2016-2017 is an increasing MAU engine. On the Android Platform that means polished UI components integrated with Google Material Design showing a visible change in UI workflow to introduce new app features with new version of the app.
The problem is if you do new app features as UI changes(its the only way that makes sense as you have to integrate with app users perceptions and worldviews) you run into UI feature back port problems. And to be blunt honest the average android developer fails at knowing android suport internals well enough to get any UI feature back-ported correctly. But, if I pay attention to android support internals and back port the UI features correctly than the UI changes to highlight new app features becomes a breeze to implement and thus we get a potential an increasing MAUs engine(my library back ports the UI features correctly and gives a solid foundation for implmenting Material Design UI components without having to worry how to back port them and thus can focus on the UI visible changes that signal a new app feature).
Since that increasing MAUs engine is focusing on grabbing M&A and or IPO results for a start-up in the form of leveraging MAUs for MA& and or IPO it might be advantageous to begin an email conversation with me if your start-up is newly funded and seeking their first android developer.