YOW Mobile Night 2011 - The realestate.com.au mobile story
Upcoming SlideShare
Loading in...5

YOW Mobile Night 2011 - The realestate.com.au mobile story



A brief summary of the path taken by the mobile development team at realestate.com.au. ...

A brief summary of the path taken by the mobile development team at realestate.com.au.

It provides an overview of the project from inception to cancellation, to rebirth, multi-platform and tablet.

The presentation concludes with some observations, on the platform, technologies and the future.



Total Views
Slideshare-icon Views on SlideShare
Embed Views



4 Embeds 146

http://www.exposecreative.net 110
http://www.exposecreative.net.dev 26
http://www.linkedin.com 8
https://twitter.com 2


Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-NonCommercial LicenseCC Attribution-NonCommercial License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    YOW Mobile Night 2011 - The realestate.com.au mobile story YOW Mobile Night 2011 - The realestate.com.au mobile story Presentation Transcript

    • 1
    • Who Am IDelivery Manager - Mobile REA Group (realestate.com.au et al) 2
    • From Concept to … 3
    • The Beginning• New to the organisation• New team• Organisation new to native mobile• High expectations 4
    • Not a Website• Native mobile is not the mobile web• REAPA (REA Personal Assistant) 5
    • We Screwed Up• The initial project was cancelled after three months (the agile process in practice)• Reset and re-imagined• Halved the team size• Doubled the productivity 6
    • Release One 7
    • Release One• Nine Weeks to Develop (including back end)• Initially rejected by Apple• Counting the appeal it took a month from submission to release 8
    • Android 9
    • Android• Two External Parties Approached• Both quoted about the same duration• Three weeks. 10
    • Android• Four Months in the Making• All experience mobile java developers• Majority of the development done in China• Completed here (with the team from China) 11
    • iOS 1.3 12
    • iOS 1.3• Bookmarking + ?• Third Party integration• Shelved waiting for Third Party• Eventually released without Third Party features 13
    • iOS 1.3• We broke it• Active error monitoring alerted us within minutes of store launch• Our only x.x.x release• 12 Hours for new version to appear in the store 14
    • iPad 15
    • iPad• Eight week schedule• Problems with unanticipated scope• Problems with defects• Five weeks in and very little was production quality 16
    • iPad• Changed the team Structure• Reduced from six to three developers• Moved two developers to automated testing• Moved two to another project• Added an experienced developer (me) 17
    • Observations 18
    • The Platform 19
    • iOS• Two screen sizes, three resolutions• Memory varies• CPU varies• Subtle UI changes coming in iOS 5 20
    • Android• Every device is different, youll need a few• Screen and resolutions vary (lots)• Touch and tap tracking vary (lots)• CPU and Memory vary (lots)• Basic UI varies (lots)• Physical keyboards 21
    • The Environment 22
    • iOS• Objective-C, rocks, seriously• xCode, sucks, getting better, very slowly• Frameworks, you need to know them• Understand, layers and views intimately• Ive never used interface builder for a production application 23
    • Android• Java, ageing gracefully, but its still Java• Alternative languages, scala, clojure, et al• Eclipse, IntelliJ, rock the house• Learning curve is in the frameworks 24
    • Memory Management 25
    • iOS• Its easier than you think• Remember the rules, you alloc or copy it, you own it• Blocks are sneaky• Listen to the system warnings• ARC is coming 26
    • Android• Garbage collection is a beautiful thing• Garbage collection sucks• Reference leaks are your enemy• Hard to dump it when you know your done 27
    • Delivering to Multiple Platforms 28
    • Respect the differences• Dont just port you application from one platform to the other• The UX is subtly (and not so subtly) different• Cross platform toolkits dont deliver (yet?) 29
    • Unified Testing• One set of acceptance tests, share the definitions• Automate what you can, be prepared to manually test what you cant• Screen comparisons are an essential part of the process• No dedicated QA for our first two releases• QA is everyones role 30
    • Summarysome closing thoughts 31
    • In My Opinion• Deliver an application that has an opinion (you cant please everyone anyhow)• Concentrate on a consistent user experience• Everyone is responsible for quality• Its not easy. Expect some good developers to fail in the move to mobile and thats okay 32
    • And• iOS is easier than Android, for now.• Ice Cream Sandwich will reduce Android device fragmentation• The Windows marketplace will be a better revenue source than The Android markets• Im going to be wrong on at least one of the point above 33
    • Questions @kevinoneill 34