{"id":577,"date":"2014-10-30T12:01:04","date_gmt":"2014-10-30T11:01:04","guid":{"rendered":"http:\/\/blog.ansuz.nl\/?p=577"},"modified":"2014-10-31T12:14:08","modified_gmt":"2014-10-31T11:14:08","slug":"droidcon-uk-day-1-2","status":"publish","type":"post","link":"http:\/\/blog.ansuz.nl\/index.php\/2014\/10\/30\/droidcon-uk-day-1-2\/","title":{"rendered":"Droidcon UK – Day 1"},"content":{"rendered":"

9.00 Barcamp planning<\/strong><\/p>\n

Getting all sessions in for the day’s talks. At the end of the day there will also be an “Appcamp” to demo applications to the audience.<\/p>\n

10.30 AIDE – Android Wear app with AIDE<\/strong><\/p>\n

Company: appfour GmbH, Speakers: Hans Kratz, Dr. Dennis Strein, Website: www.android-ide.com<\/a>.<\/p>\n

AIDE = Android Integrated Development Environment.<\/p>\n

Applications that are “Wear enabled” contain the Wear APK inside the phone APK.<\/p>\n

AIDE uses Gradle to package Wear. To enable Wear, add the following to your build dependencies:<\/p>\n

\n\n\t\t
\n\n\t\t
\n\t\t\t\t\t\t< View plain text<\/span> ><\/a>\n\t\t\t\t\t<\/div>\n\n\t\t
groovy<\/div>\n\n\t\t\n\t\t
\n\n\t<\/div>\n\t\n\t
\n\t\t
  1. wearApp project(<\/span>':wearable'<\/span>)<\/span><\/div><\/li>\n<\/ol>\t<\/div>\n\n<\/div>\n\n

    Google also has a lot of information on how to create wearable apps<\/a>.<\/p>\n

    The presentation was followed by a live demo of how to use AIDE on a device.<\/p>\n

    11.10\u00a0Modern Testing Technologies<\/strong><\/p>\n

    (or how to avoid getting murdered in your sleep by a death goblin.)<\/em><\/p>\n

    Speaker:\u00a0Mr Death Goblin a.k.a. Zan Markan<\/p>\n

    Follow SOLID<\/a> principles to increase your chances to catch a goblin.<\/p>\n

    Good tools for this include: Dagger (DI\/IoC), Mockito (mocking), Calabash, Robotium, etc. Start using the tools before you write a single line of code.<\/p>\n

    When your project grows, allow for refactoring. Split up too big methods, classes, etc. The tests should be there to help you achieve that and keep things working.<\/p>\n

    Use CI tools, like Travis, to automatically test \/ build your project.<\/p>\n

    How to deal with legacy projects? Start by covering new features with tests. Cover any code related to bug fixing with tests. Little by little the coverage will get better and better.<\/p>\n

    12.05 TDD Coverage<\/strong><\/p>\n

    Tools: GUnit (Unit tests), Robolectric, Mockito (Mocking), Emma (for coverage).<\/p>\n

    Performance testing with a monkey that visits every Activity, combine this with TraceView for profiling to measure memory usage, CPU, etc.<\/p>\n

    Testing the manifest: Use Robolectric to get a shadow application, fetch the package manager, check what service, receivers, etc are registered and verify that they exist.<\/p>\n

    12.45 Simple persistence with cupboard<\/strong><\/p>\n

    Company: LittleRobots, Speaker: Hugo Visser, Project home:\u00a0bitbucket.org\/qbusict\/cupboard<\/a><\/p>\n

    SQLite powered, using field names (from Models) to match columns. Simple usage example\u00a0<\/p>\n

    \n\n\t\t
    \n\n\t\t
    \n\t\t\t\t\t\t< View plain text<\/span> ><\/a>\n\t\t\t\t\t<\/div>\n\n\t\t
    java<\/div>\n\n\t\t\n\t\t
    \n\n\t<\/div>\n\t\n\t
    \n\t\t
    1. cupboard(<\/span>)<\/span>.withDatabase<\/span>(<\/span>db)<\/span>.put<\/span>(<\/span>person)<\/span><\/div><\/li>\n<\/ol>\t<\/div>\n\n<\/div>\n\n

      14.20\u00a0Calligraphy \u2013 Fonts in styling<\/strong><\/p>\n

      Company: YoYo, Speaker:\u00a0Chris Jenkins, Project home:\u00a0github.com\/chrisjenx\/Calligraphy<\/a><\/p>\n

      Simplifying using custom fonts on Android.<\/p>\n

      Example usage: <\/p>\n

      \n\n\t\t
      \n\n\t\t
      \n\t\t\t\t\t\t< View plain text<\/span> ><\/a>\n\t\t\t\t\t<\/div>\n\n\t\t
      xml<\/div>\n\n\t\t\n\t\t
      \n\n\t<\/div>\n\t\n\t
      \n\t\t
      1. <TextView<\/span> ... fontPath<\/span>="fonts\/your_font.ttf"<\/span>><\/span><\/span><\/div><\/li>\n<\/ol>\t<\/div>\n\n<\/div>\n\n

        15.55 Y U No craftsman!?<\/strong><\/p>\n

        Company: Novoda, Speakers:\u00a0Paul Blundell and Xavi Rieau<\/p>\n

        Ways to create better code \/ be a better craftsman.<\/p>\n

        Pair programming, best coding practices, code reviews. Care about CI, show build status (i.e. on a big screen in the office). Run static analysis reports. Test!<\/p>\n

        To make things more fun: CI Game (Jenkins plugin), creates a monthly leaderboard.<\/p>\n

        Use the latest tools with your work.<\/p>\n

        Be “agile”, build features the way they make sense. Believe in YAGNI (you ain’t gonna need it), don’t over-engineer.<\/p>\n

        Make your app awesome:<\/p>\n