Unity UI Storyboard
🇺🇸English
🇰🇷Korean🇺🇸English
🇺🇸English
🇰🇷Korean🇺🇸English
  • UI Storyboard
    • Sample Project
    • 概要
      • References
      • Dependencies
      • Overall structure diagram
      • Key Design Concepts
        • Onion Architecture
        • MVRP Method (Model-View-Reactive Presenter)
        • UI/UX Design Principles
        • Principles for using Reactive libraries
        • About the MVP concept
        • Model, View, Presenter (Lifecycle)
        • Test & Mockup Policy
        • Managing code dependencies and .asmdefs
    • Quick Start
      • 安装
      • Project Initialization
        • Using automatic initialization
      • [Planners] Organizing your first storyboard
        • Determining the reference resolution
        • Page and Modal
        • Creating a Storyboard
        • Add a Page node and a Modal node
        • Representing screen movement
        • Configure a simple mockup UI
        • Adding a mockup UI to a storyboard
        • Leave notes
        • Finalize your storyboard
      • [UI/UX Designer] Designing the UI
        • Organizing screens
        • Organizing with prep
        • Updating your storyboard
        • Tips for newbies
      • [Developers] Write your first UI code
        • See an example of implementing a login modal window
        • View
        • Lifecycle (presenter)
        • Model (ViewModel)
        • Builder
        • LifetimeScope
        • RootLifetimeScope
        • UseCase
        • Repository
        • Gateway
      • [Developers] Writing test/mockup code
        • The power of mockup code
        • Writing mockup code
      • Finished mockup UI
  • UnityScreenNavigator
    • Lifecycle
  • ScreenSystem
    • Understanding the concept
      • What is an out game?
      • Dependencies
      • Relationship to UnityScreenNavigator
      • Class design
      • Implementation Sample Project
    • Core Components
      • LifetimeScope
        • RootLifetimeScope
      • Lifecycle
      • Model
      • View
      • Builder
      • UseCase
        • About the timing of communication processing according to screen switching
      • Repository
    • Screen-to-screen messaging with MessagePipe
Powered by GitBook
On this page
  • Development Units
  • About using the interface
  • The actual logic is
  1. UI Storyboard
  2. 概要
  3. Key Design Concepts

Model, View, Presenter (Lifecycle)

Development Units

  • The default unit is 1 Presenter, 1 View, and 1 ViewModel per Page/Modal.

  • Depending on the complexity, you can configure multiple ViewModels or Views, but it is recommended that they are ultimately "merged" into a single View.

  • In a real MVP, the Model role is played by a Repository, which may be shared and used in multiple places. (See Onion Architecture)

About using the interface

For more information, see the About the MVP concept Note

  • MVPs are based on direct implementation without using interfaces.

  • However, only in limited cases where we find repetitive usage more than 2-3 times throughout the project, we will discuss and extract it into an interface.

The actual logic is

  • Presenter must perform logic through UseCase, and UseCase handles external communication (servers, DBs, etc.) through Repository.

  • Repository, in turn, is responsible for the actual communication via Gateway.

  • At the UseCase level, you don't need to worry about communication conventions, protocols, etc.

  • Gateway is developed according to the actual communication protocol API, etc.

  • Repository is developed last, as an intermediary between UseCase and Gateway.

PreviousAbout the MVP conceptNextTest & Mockup Policy

Last updated 1 month ago