We’re happy to welcome Vitaliy asa speaker, for the 2nd time at MobOS. He will be also holding a workshop during the second day, besides the talk on the presentation day.
If you remember him from 2016, Vitaliy still does quite a lot of things in the Android arena: besides being a mobile developer, he’s also a public speaker and a community manager. He’s mostly interested in GameDev, Android, iOS, wearables and community management. Vitaliy is eager about product perfection and scalability and he really goes crazy about new IoT devices and Google products. In Ukraine, where Vitaliy is from, he founded the Google Developer Group of Lviv.
Currently he is Head of Mobile at GetSocial, a startup based in The Netherlands. GetSocial is building a cloud-based mobile engagement platform that empowers any app developer with tools to maximise user acquisition, engagement, retention and monetization.
His talk will be around the “Key learnings and pitfalls from building mobile SDK“
Are you working on the client library? Or design a public API for the module that is going to be used by other team or department?
In this session, Vitality will share his experience and key learnings from building a set of mobile SDKs. The session will be interesting for Android and iOS developers who want to learn what makes client library great. What are the best practices and common pitfalls in public API design. What is important, only programming API you expose or also ecosystem around?
His workshop will be around “TDD and software architecture, or let’s play some bowling.“
Test Driven Development. During the workshop, Vitaliy will use the three laws and the Red-Green-Refactor cycle to implement the algorithm for scoring games of 10-pin bowling. We will start with running a quick UML design session. Then TDD commences, we will create the algorithm by applying the three laws of TDD in the Red-Green-Refactor cycle. Finally, we will compare the end result to the initial design.
In the second part of the workshop, you’ll have a chance to try TDD on your own.
Get your testing environment ready. All examples will be in Java, but for the hands-on part any language you’re comfortable with will work.