Droidcon 2011 - Branding Headache? Here's Your Painkiller


Published on

Some useful tips and techniques for developing mobile apps across multiple different brands, presented by mobile developer, Joana Cruz e Costa, at Droidcon 2011.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • I’m an android developer at Masabi, a company that masters in developing apps for passengers to securely buy and display tickets on their phones.
  • It might be better to show you a promo video of what we do, rather than talking about the company itself.
  • 10
  • Developers of mobile applications know exactly how difficult and frustrating app coding can sometimes get. The problem intensifies further while writing code for multi-branded mobile applications. Each brand wants its own set of features, color schemes, images, text and so on. How can we ease the pain ? Create an ant target for each of your brandings. For each single target you can add different files (e.g. images) and set an app name. You can even use the same file names (but stored under a different location) and you can build your brand-apps pretty fast.The main downside comes when you have lots of different brands and/or lots of different resources. Changing any aspect of the branding (adding/removing/renaming resources) can become quite tedious.
  • Branded resources :We then have an automated build script that generates this folder according to the brands that are committed in the Resources Project (*our UKRailResources project*) that has all the resources (values, texts colours, dimensions, images, etcetc) for all the brands
  • Droidcon 2011 - Branding Headache? Here's Your Painkiller

    1. 1. Branding Headache?<br />Here’s your painkiller.<br />Joana Costa | October 2011<br />
    2. 2. Branding headache? | Here’s your painkiller<br />Painkiller Summary<br /><ul><li>Separatebrandingfromdevelopment
    3. 3. Avoidhasslingdeveloperswith design issues
    4. 4. Quicklybuild for multi-brandedapplications
    5. 5. Re-use common branding assets
    6. 6. Automate branding process</li></li></ul><li>Branding headache? | Overview<br />MasabiOverview<br />Leading developer of mobile ticketing. <br />End of ticket queues by allowing passengers to quickly, securely buy and display train tickets on almost any mobile phone.<br />
    7. 7. Branding headache? | Overview<br />Masabi<br />Overview<br />demo<br />
    8. 8. Many platforms, many brands<br />Branding headache? | Overview<br />Other Phones<br />
    9. 9. Branding headache? | Here’s your painkiller<br />Developing for multi-branded mobile applications<br />
    10. 10. Branding headache? <br />Branding headache? | Here’s your painkiller<br />
    11. 11. Branding headache? | Here’s your painkiller<br />Resource project<br />strings<br />SVN commit<br />images<br />Android specific resources<br />Update to <br /> head<br />properties<br />Android project<br />Build.xmlCopies all resources from branded resources to the android res folder<br />Android run with branded res<br />
    12. 12. Branding headache? | Here’s your painkiller<br />Layout folder – card_details_activity.xml<br />Not branded<br />styles.xml<br />branded<br />
    13. 13. Make your life easy<br />Separate content from style<br />Standardize and automate<br />Focus on development by enabling other people to do the “boring stuff”!<br />
    14. 14. Any Questions?<br />(...and yes, we are recruiting! If you are shy, just send your CV to joana@masabi.com)<br />