App architecture101
Using a patient-facing app as our primary case study, we'll learn: * How are apps made? * How much does development typically cost? * How YOU can design your own app (and maybe even develop it!). * What can apps do? What can't they do? * What's a good use case for an app? * What's a web app? What's a native app? When would I want to prefer one over the other? * How can I build an app on a zero-dollar budget? And what if I had all the money in the world? * How do I find a good programmer? How do I build a good development team? Alternatively, how do I build an app without a programmer? * How to make smart technology decisions. * Buy vs build? * How to manage an app develoment project. * What you need to know about HIPAA and FDA regulation. You can also expect a brief intro to programmer culture, Windows vs Linux, and how your business can benefit from open source. And, finally, we'll touch on business models for healthcare apps. ======================================= About the Speaker: David Kay is a on a mission to simplify medical diagnostics by wielding modern technology. He currently leads software development at SALT, a medical device startup focused on bringing hassle-free salt monitoring to patients at home. Happy to have been a Google engineer, and even happier to have rapidly resigned, David feels most alive when pushing his own boundaries and the stakes are high. He was the founding CTO at EnHatch, which provides sales and marketing technology to medical device companies, and the founding CTO of Authy, a security startup which was recently acquired by Twilio. David also deeply enjoys teaching, and has led mobile development workshops at Princeton University and Rutgers University, taught Ruby on Rails at iHub Nairobi, and served as an Android instructor at General Assembly. His technical achievements include: * Winner of the MIT Telehealth grand prize and the Merck Telehealth grand prize at the MIT Hacking Medicine Grand Hack * Winner of "best design/best prototype" at the Yale Patient Experience Hackathon * 3rd place at GHG Patient Outcomes Hackathon * 2x Global finalist at NASA Space Apps Challenge * 2x semi-finalist of StartupBus SxSW * 2nd place at TechCrunch Disrupt San Francisco * 2x featured for "Hack of the Month" at New York Tech Meetup * Led development on several pioneering iPad apps for Otsuka Medical * Led an 7-man team to build an app in only 3 weeks for a debut on Shark Tank * Project lead on the Android app for 1-800-GOT-JUNK's worldwide truck fleet * iPad lead for Deutsche Bank's first mobile app, GlobalPrime Apart from his love for medical technology, David is also an avid inline skater and certified skate instructor. You can reach David at: davidykay@gmail.com
Recommended
Recommended
More Related Content
What's hot
What's hot (17)
Similar to App architecture101
Similar to App architecture101 (20)
More from David Kay
Recently uploaded
Recently uploaded (20)
App architecture101
- 1. Healthcare App Architecture 101 David Y. Kay
- 2. If you can design a system, you can build an app.
- 3. What can an app do? • Dumb question? • No way. Let’s explore.
- 5. Wearables
- 6. What can computers do? Math. Or things that can be reduced to math.
- 14. But how?
- 16. Moore’s Law
- 17. Moore’s Law
- 19. Design User Flow Wireframes Mockups
- 20. Design
- 27. Web vs Native
- 28. Web vs Native Native Hybrid Web Application iOS / Android HTML & Javascript Firefox iOS / Android iOS / Android HTML & Javascript Application Embedded Browser
- 30. Windows vs Linux
- 31. Open Source
- 32. Open Source Benefits • Hiring • Re-use • Reduce maintenance cost • Better modularity
- 33. Cloud ?
- 35. Buy vs Build • Is this your differentiator? • How is the documentation / support?
- 36. Hiring • In-house • On-site • Remote • Contract • USA • Overseas
- 38. Culture
- 39. “$78,755 per year” payscale.com Developers are expensive
- 40. hardware: Make efficient use of expensive computer… programmers:
- 41. “hardware is cheap - and programmers are expensive” -Jeff Atwood
- 42. “the constraints imposed in building large software systems are the limitations of our own minds.” -Hal Abelson
- 44. Correctness • Is someone going to die if something goes wrong? • Fitbit? Not a problem. • Pacemaker? Big problem.
- 45. You can do it yourself! • Programming is not just for wizards • …and you don’t necessarily need to learn it! • Ari’s IFTTT example
- 46. Codeless Apps
- 47. Hardware
- 48. What’s it cost? • $5K - millions. • [Cite some numbers here]
- 49. Regulatory
- 50. FDA
- 51. Predicates
- 52. Additional Resources • Rock Health: The Entrepreneur and the FDA • FDA Webinar on Digital Healh
- 53. HIPAA • Privacy Rule • Security Rule • BAAs
- 54. BAAs Hardware OS Application VM You’re on your own! It’s on Amazon. } }
- 55. Cloud, Revisited Hardware DIY Cloud Managed OS Application VM Hardware OS Application VM Hardware OS Application VM
- 56. Revenue Models • One-time purchase • In-app Purchase • Subscription • Advertising • Others
- 57. Who is your customer? • Consumer • Provider • Med device / Pharma
- 58. Reimbursement • Coding • Reimbursement Consultants
- 59. Key Question • How does this add value?
- 60. Do I need an app? • Use the minimal effort to achieve a great solution • Often this is a tricky thing to accomplish
- 61. “If this app were an employee, what would its job description be?” -Brennan Dunn
- 62. Recap • If you can design a system, you can build an app • Hardware is cheap, programmers are expensive • Focus on what matters
- 63. Let’s wind up.
- 64. Recommended Reading • Joel on Software - The business of Software • Paul Graham - Startup & Hacker Culture • Steve Yegge - Rants on programming culture • Ray Kurzweil - The Singularity is Near