Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Rich Client Design Patterns
Search
bradgignac
April 14, 2012
Programming
3
260
Rich Client Design Patterns
Patterns for building rich client applications.
bradgignac
April 14, 2012
Tweet
Share
More Decks by bradgignac
See All by bradgignac
Why You Might Not Need Yet Another Environment
bradgignac
1
520
Understanding the Shift to Mobile
bradgignac
0
320
Front-End Operations
bradgignac
4
660
Intro to CoreOS
bradgignac
4
1.1k
Web Components and the Future of JS Frameworks
bradgignac
3
660
Modular CSS
bradgignac
0
10
Other Decks in Programming
See All in Programming
Composing an API the *right* way (Droidcon Berlin 2024)
zsmb
1
450
HMSコンペ 11th Solution (team : kansai-kaggler)
t88
1
680
しくじり先生 Image Matching Challenge 2024 編
goosehaaan
0
810
Folding Cheat Sheet #7
philipschwarz
PRO
0
150
【Go言語】ジェネリクス
tomo1227
0
170
AWS初心者ってどうやってAWSを学ぶ?〜アプリエンジニアがやってよかったアーキテクチャ学習方法〜
yamanashi_ren01
0
190
Javaの現状2024夏 / Java current status 2024 summer
kishida
4
1.4k
日付と正規化
megmogmog1965
0
140
유연한 Composable 설계
l2hyunwoo
0
380
「2024年版 Kotlin サーバーサイドプログラミング実践開発」の補講 〜O/Rマッパー編〜
n_takehata
2
260
はしめてのプログラミングとロボット制御
watawatavoltage
0
290
Polarsの成長: v0.14からv1.0までの変遷と今後の展望
zerebom
1
350
Featured
See All Featured
GitHub's CSS Performance
jonrohan
1026
450k
Agile that works and the tools we love
rasmusluckow
325
20k
Adopting Sorbet at Scale
ufuk
71
8.8k
Designing the Hi-DPI Web
ddemaree
276
34k
Docker and Python
trallard
37
2.9k
Raft: Consensus for Rubyists
vanstee
134
6.5k
StorybookのUI Testing Handbookを読んだ
zakiyama
15
4.9k
The Cost Of JavaScript in 2023
addyosmani
31
4.7k
Why You Should Never Use an ORM
jnunemaker
PRO
51
8.9k
Six Lessons from altMBA
skipperchong
24
3.2k
From Idea to $5000 a Month in 5 Months
shpigford
377
46k
Bootstrapping a Software Product
garrettdimon
PRO
304
110k
Transcript
Rich Client DESIGN PATTERNS
What is a Rich Client? A stateful application that uses
client-side business logic in order to provide the user with an improved experience.
MVVM MVP MVC
MVVM MVP MVC
MVC Communication Model View Controller
Architecture MVC Data Access Layer Business Logic Layer View Controller
MVC Key Points Reuse through nested view/controller pairs Observer and
strategy patterns decrease coupling Tied directly to domain model View code can be difficult to test
MVVM MVP MVC
MVP Communication Model View Presenter
Architecture MVP Data Access Layer Business Logic Layer Presenter View
MVP Key Points Reuse by using presenter with multiple views
More obvious interaction than MVC View decoupled from domain model Mockable views for easier testing
MVVM MVP MVC
Communication MVVM Model View View Model
Architecture MVVM Data Access Layer Business Logic Layer View Model
View
MVVM Key Points Reuse through nested views Observer pattern decreases
coupling View decoupled from domain model View model is easily testable
Any Questions?