Skip to content


Boston, MA

Mike DeMaso I'm a Software Engineer currently located in Boston, MA. I have 10+ experience in Software Development with the last 6 in Mobile and 4 in Android App development. I have taken on roles from Senior Engineer, Tech Lead, Team Lead, Engineering Manager, Software Architect, to Associate Director of Mobile Engineering. Currently I'm a Principle Software Engineer at DraftKings where we are using technology to deliver more immersive and realtime Daily Fantasy Sports and Online Sportsbooks to fans of all sports, from the NFL™️ to Rocket League®.

Latest Post - Via DraftKing Engineering Blog

MVVM Diagram

How do you achieve a responsive user interface while keeping your code clean, precise, readable, and maintainable? This is a question that has been bouncing around the brains of Android developers since 2008.

After many years of letting Android developers figure it out on their own, Google has recently given some guidance on the topic with their Guide to app architecture that promotes a variant of MVVM. While this is a great start, it leaves a lot of questions lingering for teams to answer on their own. Google also provides libraries like LiveData, Room, and DataBinding to help us reduce boilerplates and separate our code’s concerns. Even third parties have lent a helping hand with RxJava and Retrofit, which gives us an easy way to handle asynchronous work and fetch things over the network. With all of these things floating around solving small pieces of the larger question, how can we bring them all together to provide a fluid UI experience that is simple to implement and maintain?