MVP Architecture

suggest change

Introduction

MVP is an architectural pattern, a derivation of the Model–View–Controller. It’s represented by three distinct components: Model, View and the Presenter. It was engineered to facilitate automated unit testing and improve the separation of concerns in presentation logic.

In examples you’ll find a simple project built with MVP pattern in mind.

Remarks

Components:
Component duties:

| Model | View | Presenter | | —— | —— | —— | | Communicates with DB layer | Renders data | Performs queries to the Model | | Raising appropriate events | Receives events | Formats data from Model | | | Very basic validation logic | Sends formatted data to the View | | | |Complex validation logic| |||

Differences between MVC and MVP:
Pros:
Cons

Feedback about page:

Feedback:
Optional: your email if you want me to get back to you:


MVP Architecture:
* MVP Architecture

Table Of Contents
12 UIView
15 UIColor
26 UIImage
28 CALayer
30 NSDate
40 iBeacon
49 NSTimer
79 NSURL
87 AWS SDK
96 NSData
101 Segues
104 EventKit
105 NSBundle
106 SiriKit
111 StoreKit
117 3D Touch
119 Keychain
122 Block
141 AirDrop
144 UISlider
145 Carthage
146 HealthKit
151 plist
157 MVVM
164 UIPhoenix
166 Simulator
168 NSArray
169 OpenGL
172 MVP Architecture
175 Core Data
179 MyLayout
180 UIFont
189 Security
200 Codable