WHY IT MATTERS: Digital Transformation

Developing fully native applications is like buying a sports car: it’s a fun, full-featured option, but typically expensive and not always the most practical. It should be done after carefully weighing the product’s budget, the mobile app’s strategic importance, and capabilities of the current team.

Below are some guidelines to help you decide which tech stack would best fit your application. The best decision is rarely obvious and can usually only be made after a thorough cost-benefit analysis.

For the past five years, our Android project has maintained a similar package structure from when it was first created in 2012. 

We also want to keep our package structure clean. This rethought is about keeping the workspace that we interact with on a daily basis both tidy and organized.

So we set about to rethink the entire package structure of the Buffer Android app. I’m excited to share what our process looked like and all that we learned, and it’d be great to hear your thoughts and questions, too.