Architecting apps - Can we write better code by planning ahead?
Creating a successful app is like erecting a house. The building part can become laborious, boring and dangerous at times, especially if very little attention is paid to the planning process and no blueprints are to be found; in some cases it leads to disastrous outcomes, unhappy stakeholders and overrunning costs. The initial phase of understanding the client’s idea and expectations is the most critical and yet the least talked about: translating requirements into a well structure document is what makes or breaks an app – similar to creating a good architecture document before commencing work on a building. In this talk, Paul will talk about the things a team should implement before writing a single line of code (diagrams, sketches, prototypes, etc) and affix yet another acronym to the corporate bingo list: DDD (Documentation-Driven Design).
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie Architecting apps - Can we write better code by planning ahead?
Ähnlich wie Architecting apps - Can we write better code by planning ahead? (20)
Mehr von Paul Ardeleanu
Mehr von Paul Ardeleanu (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Architecting apps - Can we write better code by planning ahead?
- 1. Architecting apps Can we write better code by planning ahead? Paul Ardeleanu @pardel
- 2. Thank you
- 3. Architecting apps Can we write better code by planning ahead? Paul Ardeleanu @pardel
- 17. 100 000 000 000 app downloads
- 26. Solutions A. Respect the process B. Prototype C. Divide & Conquer D. Testing E. Documentation
- 28. Ask the right questions • usually starts with an idea / project requirement • sell the vision to the team • shoot the idea down and scale according to the platform constraints • communication, communication, communication • proposal
- 30. Application Definition Statement “A concise, concrete declaration of the app’s main purpose and its intended audience.” https://developer.apple.com/library/ios/documentation/ UserExperience/Conceptual/MobileHIG/
- 31. Solve real problems "An app must solve a user's problem clearly and elegantly." Eric Hope, User Experience Evangelist, Apple
- 32. List of features too many features? Filter Yes Application Definition Statement App features User journeys Wirefames Prototype
- 33. Prototype
- 35. Wireframing • identify main areas of the app • identify screens • identify relations between screens • start from the simplest things and build up • start from the main task of the app
- 36. Sketching
- 37. Sketching
- 38. Sketching
- 39. Sketching
- 40. Sketching
- 41. Sketching
- 42. Sketching
- 43. Sketching
- 44. Sketching
- 45. Sketching
- 46. Sketching
- 47. Sketching
- 48. Sketching
- 49. Sketching
- 50. More sketching start Splash screen List of sequences Add sequence Sequence edit 05:12start Timer start Add timer
- 51. Sketching • start from the most important task • identify main areas of the app • identify screens • identify relations between screens • Don’t worry! You won’t get it right the first time
- 52. Prototyping • Web based • Visual • Presentation based
- 53. Divide & Conquer
- 54. C4 Model
- 55. C4 Model
- 56. C4 Model
- 59. Black Box • Avoid side effects • Control inter-dependencies • Improve testability
- 61. Playgrounds
- 62. Testing
- 63. Faster is always better
- 64. Faster is always better
- 65. TDD vs BDD • Test-Driven Development • Behaviour-Driven Development
- 67. Documentation
- 68. UML The Unified Modelling Language (UML) is a general-purpose modelling language in the field of software engineering, which is designed to provide a standard way to visualize the design of a system.
- 69. UML
- 70. Documentation • Sanity • Communication across multiple teams • Inter-operability of features • Good practices • Sanity
- 71. Solutions A. Respect the process B. Prototype C. Divide & Conquer D. Testing E. Documentation
- 72. Off by 1
- 73. Motivation
- 79. Your Why
- 81. Charity
- 82. Help people
- 84. Solutions A. Respect the process B. Prototype C. Divide & Conquer D. Testing E. Documentation F. Motivation