User
What should be written in the user story in the basic design of mobile application development?
ChatGPT
User stories are an important element in the basic design of mobile app development. A user story is a technique for defining an app’s features and functional requirements from the user’s perspective. Here are some examples of what you should include in your user story:
User Roles: Clarify the roles and characteristics of users who use your app. For example, general user, administrator, member, etc.
User Intent: Describes the user’s purpose or goals for using the app. For example, to purchase products, search for information, edit your profile, etc.
Actions: Concretely describe the actions or operations that the user should perform. For example, clicking a button, uploading an image, entering a search query, etc.
Expected Result: State the desired result or behavior of the action taken by the user. For example, information is displayed, notifications are received, success messages are displayed, etc.
Importance/Priority: Set the importance/priority of each user story. This allows you to prioritize development and allocate resources.
Supplemental Information: If necessary, include additional information, restrictions, or special notes related to the user story.
User stories are shared among development teams and stakeholders to help design and prioritize app features. User stories are also used as a reference during testing and validation.
User
What should be described in the user flow in the basic design of mobile application development?
ChatGPT
A user flow is a design element that expresses specific steps and screen transitions when a user uses an app. Below are examples of elements that should be included in the user flow in the basic design of mobile app development.
User starting point: Clearly indicate the screen or state where the user flow starts. For example, app home screen, login screen, etc.
Actions: Concretely describe the actions or operations that the user should perform. For example, clicking a button, entering text, swiping the screen, etc.
Screen transitions: Show screen transitions caused by actions performed by the user. For example, transition from the home screen to the details screen, display a menu, or display a popup.
Conditional branching: Explicit conditional branching when different paths are followed depending on certain conditions. For example, transition to the login screen if you are not logged in, transition to the administrator screen if you have specific privileges, etc.
Back action: Indicates an action or transition that takes the user back to the previous screen. For example, clicking the back button, back with a swipe gesture, etc.
Completion State: At the end of the user flow, indicates when the user has completed a specific goal or task. For example, an order has been placed, payment has been completed, a form has been submitted, etc.
User flows play an important role in designing app navigation and screen transitions. It is shared by the development team and designers and serves as a reference when considering the usability and operation flow of the app.
