- The document outlines the design process and how it benefits mobile developers. The design process includes entry phase, prototyping, delivery, analytics, and feedback. - During each phase, developers gain business and user insights, scope definitions, and visual designs that help with estimations and technical decisions. Developers provide expertise, ideas, prototypes, and code integration in return. - The design process ensures developers understand user needs which allows them to build the right solutions and continuously improve through analytics and user feedback.

1. Mobile Dev & Design
What developers get
from design process
Kamil Szwaba
Mobile Team Leader

2. Mobile Dev & Design
Agenda
Entry Phase Prototyping Delivery Analytics Feedback

3. Mobile Dev & Design
Agenda

4. Entry Phase
Main question: check if we are
solving the right problem

5. Entry Phase
#1
Workshop
#2
Competition research
#3
User journey
#4
Backlog definition

6. Entry Phase
Artiffacts Examples
―Personas
―MVP backlog
―Wireframes
―Business goals

7. Entry Phase
Developers
What they GET
— Business overview
— User overview
— Project scope
— Inputs for technology selection
— Infrastructure description
What they GIVE
— Ideas with technology capabilities
— Technology recommendation
— Expertise over what is possible
— Easier/safer/cheaper solution selection
— Priorities based on dependencies

8. Prototype
Fast solution verification

9. Prototype
#1
Most important path
#2
UI design
#3
Mocked data
#4
Clickable

10. Prototype
Artiffacts Examples
―General look & feel
―Main theme
―First feedback

11. Prototype
Developers
What they GET
— Better scope definition for estimations
— General look and main flow of the
application
— Feeling of the solution
What they GIVE
— Possible development of mocked
prototype
— Estimations for prototype development

12. Delivery
Team working with user-
centric approach

13. Delivery
#1
Agile Team
#7
UI/UX/BA contributing
#3
Application development
#
4
Tests
#5
Scrum ceremonies
#2
Sprint goals
#6
Conceptual work
#8
Regular releases

14. Delivery
Artiffacts Examples
―Released application
―Backlog defined (documantion)
―User paths
―Graphic designs

15. Delivery
Developers
What they GET
— Graphic designs with assets and definitions
— Support when elements are missing or not working
(adjustments)
— Quick verification after functionality is developed
— Visibility into business goals
— Stories clarification
What they GIVE
— Ideas
— Estimates
— Development work
— Assets format definition
— Regular releases

16. Analytics
Collecting data can
speed up the success

17. Analytics
#1
Goals
#2
Events
#3
User profile
#4
Devices

18. Analytics
Artiffacts Examples
―User Stats
―Business Stats
―Device Stats

19. Analytics
Developers
What they GET
— Information about errors​
— Devices and system version stats​
— Users count
What they GIVE
— Integration of analytics tool​
— Code for collecting events and goals

20. Feedback
This is the end of one iteration
and start for next

21. Feedback
#1
Users comments
#2
Analytics data
#3
Ratings
#4
Errors count

22. Feedback
Artiffacts Examples
―What is done right
―What is done wrong
―What is most important
―What should be removed

23. Feedback
Developers
What they GET
— Enhancements description​
— New scope​
— Better user uderstanding
— Motivations and greetings
What they GIVE
— Plan for error count reduction​
— Technical expertise for ehancements and new scope​
— Ideas​
— Estimations

24. Design puts developers
closer to the users.
Kamil Szwaba
Mobile Team Leader

25. Thank you
pgs-soft.com
kszwaba@pgs-soft.com