This document summarizes the experiences of porting a clinical mobile application called NeuroMind from iPhone to Android using online collaboration. NeuroMind was originally developed for iPhone and provides medical resources. The authors, a medical student and neurosurgeon, collaborated online to develop an Android version after being contacted on Twitter. They encountered challenges with different development environments and platforms, as well as maintaining collaboration over long distances. Future work may involve improving the user interface for multiple platforms and integrating content collaboration tools.

1. Porting a Clinical Mobile Device Application from iPhone to Android using Online Collaboration:a Case Study using NeuroMindJonathan C. Lau, MEng, MD Candidate, Queen’s UniversityPieter Kubben, MD, PhD, Maastricht University

2. ObjectiveTo present our experiences porting a clinical mobile device application, NeuroMind, from iPhone to AndroidSuccesses we’ve obtainedChallenges of online collaboration

3. OutlineWhat is NeuroMind?Our CollaborationWhy Android?Project PlanningProject DevelopmentChallengesFuture Work

4. OutlineWhat is NeuroMind?Our CollaborationWhy Android?Project PlanningProject DevelopmentChallengesFuture Work

5. NeuroMindA mobile device application developed originally for the iPhone by Dr. KubbenSpecifically designed as clinical resource for:medical studentsneurology / neurosurgery residentsneurologists / neurosurgeonsAvailable on the AppStore as free downloadDetails at: http://blog.digitalneurosurgeon.com

6. NeuroMind

7. NeuroMindHas been downloaded more than 30,000X since its release#1 ranked iPhone app for neurosurgery

8. OutlineWhat is NeuroMind?Our CollaborationWhy Android?Project PlanningProject DevelopmentChallengesFuture Work

9. CollaborationHow does a medical student from Kingston, Ontario, Canada end up collaborating with a neurosurgery resident from Maastricht?

10. CollaborationSocial Media (Twitter)

11. CollaborationAfter two readers emailed @DigNeurosurgeon about NeuroMind on Android, he broadcasted the following message on Twitter:Link to his blogConcluded that it was outside of his current priorities to port NeuroMind to AndroidBut should anyone be interested, to contact him

12. CollaborationIn touch by email that dayAgreed on initial plan:To develop framework in Android SDKAdd same content as on iPhone (HTML)Tentative deadline for working application:Six months from our initial contact(Time of Medicine 2.0 Congress)

13. OutlineWhat is NeuroMind?Our CollaborationWhy Android?Project PlanningProject DevelopmentChallengesFuture Work

14. Why Android?

15. Why Android?

16. Why Android?

17. OutlineWhat is NeuroMind?Our CollaborationWhy Android?Project PlanningProject DevelopmentChallengesFuture Work

18. Project Planning

19. Project PlanningGoogle Wave:Google stopped developing 2010/08.

20. Project Planning37signals Basecamp: www.basecamphq.com30-day free trial then $49/month.

21. Project PlanningEmailJuly:get Dictionary example workingexperiment with changing content in exampleAugust-September: expand example withworking database in background that is used for loading datahave the user go to a detail screen that displays the data (title, description, content) if the user clicks the item in the TableViewOctober:Populate app with actual content and continue testingNovember: prepare conference material and releaseNov-Dec: release and post about it

22. Project PlanningObtaining an Android phoneNot absolutely necessary: well-documented software from Google for virtual deviceBought used HTC Magic onlineObtaining an “iProduct” to evaluate NeuroMindBorrowed an iTouch from colleague

23. OutlineWhat is NeuroMind?Our CollaborationWhy Android?Project PlanningProject DevelopmentChallengesFuture Work

24. Project DevelopmentSoftware Development EnvironmentOriginal goal to try developing using Android SDKEclipse Platform:Free open-source softwareDesigned for development of Java applicationsAndroid SDK available with virtual device for testing mobile device applications

25. Project DevelopmentTutorials on Android (http://developer.android.com)Hello World to DictionaryListView as UI candidate

26. Project DevelopmentEnter Appcelerator Titanium Mobile 1.4Released July 26, 2010Open source platform for developing native mobile and desktop applications using web technologiesSupport for multiple platforms:iPhone and Android support since June 2009iPad support since April 2010Blackberry support in beta

27. Project DevelopmentSignificant progress with Appcelerator1.4 release (September/October 2010)Preliminary Android NeuroMind released:October 23, 2010 (ahead of schedule!)Coincided with release of Surgical Neurology International mobile applicationsee conference presentation by Kubben et al.

28. Project DevelopmentAvailable on Android Market

29. 500-1000 downloads so farOutlineWhat is NeuroMind?Our CollaborationWhy Android?Project PlanningProject DevelopmentChallengesFuture Work

30. ChallengesIn Medicine 2.0 context:Selected Group of Stakeholders:Neurosurgeons and neurologistsNeurosurgery and neurology residentsMedical students interested in clinical neuroscienceCollaboration:Limited to specialized # of stakeholders who also had interest in mobile device application developmentLikely did not take advantage of expertise of greater community as well as we could have

31. ChallengesCollaborator Idiosyncrasyor “Compatibility” between collaboratorsDifferent Platforms:Lack of virtual device on non-Apple products for product developmentDifferent Software Development Environments:Eclipse Java environmentAppcelerator TitaniumTime:Clinical duties, other research priorities, time difference

32. ChallengesMaintaining CollaborationWe know Medicine 2.0 is useful for initiation of collaboration (intermediation/apomediation) but how do we maintain effective collaboration over time?

33. ChallengesCollaboration in Software DevelopmentTracking Project MilestonesSocial Media: Twitter, Google Wave37signals BasecampTracking Software ChangesRedmine:web-based project management + bug-tracking toolTracAppcelerator?

34. ChallengesCollaboration in ContentTracking Content Changes (neurodss.com)Currently using Google DocsAlternatives:Wiki

35. OutlineWhat is NeuroMind?Our CollaborationWhy Android?Project PlanningProject DevelopmentChallengesFuture Work

36. Future WorkDesign, Development, Maintenance, TestingUser Interface (iOS, Android, RIM, Windows 7)Appcelerator has many advantages:Content / Layout nuances decided by othersSoftware development largely outsourcedCan focus on content buildingThere are disadvantages too:Dependence on support provided by company and their roadmap for developmentProfessional version $199/developer/month

37. Future WorkCollaboration in ContentMobilize other stakeholders??Authority to edit?Authority to edit from mobile deviceAbility to rate entriesAbility to ask for new entriesPeer-reviewAside: need to support multiple mobile platforms to ensure widest participation

38. Future WorkMultiple Versions of NeuroMind?Decision support version for cliniciansEducation version for medical studentsIntegration with Neurosurgery 2.0 framework?

39. Future Work

40. Future Work

41. ConclusionsWhile our software development deviated from our original design, a product was released ahead of schedule for AndroidOnline collaboration can be effective but the tools used are context dependent and depend also on project scale and directionHaving the opportunity to discuss in person at this meeting will greatly assist with facilitating our continued collaborations

42. AcknowledgementsDr. Pieter L. Kubben (@DigNeurosurgeon)Maastricht UniversityQueen’s University, Kingston, ON, CanadaDr. Richard ResnickDean of the Faculty of Health Sciences for fundingUndergraduate Medical Education Office

43. Thank you for your attention!Questions?