+ All Categories

Home > Technology > Adapting View Models as a Means For Sharing User Interface Code Between OS X and iOS

Adapting View Models as a Means For Sharing User Interface Code Between OS X and iOS

Date post:	09-May-2015
Category:	Technology
Upload:	dileepa-jayathilake
View:	364 times
Download:	1 times

Download Report this document

Share this document with a friend

Description:

This work describes a solution to a costly problem that surfaces in software product engineering on Objective C technology stack. Particularly, it emerges when designing a software product targeting both OS X and iOS where a significant part of the functionality is common for both platforms. This brings in the question of how much code can be reused between the two implementations. A multitude of concerns need to be probed and the solution domain can easily be a victim of combinatorial explosion. Like in many other cases, analysis in terms of design patterns can put things in perspective. Both Cocoa and Cocoa Touch (standard frameworks for application development in OS X and iOS respectively) highly encourage embracement of MVC as a design pattern. It is even a necessity for utilizing certain parts of the two frameworks. Therefore, it is wise to keep our solution inside the MVC design paradigm. Our exploration to the solution starts with a close examination of MVC and the role played by each component in the design pattern. Controllers in both Cocoa and Cocoa Touch are responsible for managing views and responding to user actions, embracing Strategy pattern. They are tightly bound to the views they control and therefore are hardly useful outside the context of that particular view. At the same time views and controllers in OS X (based on NSView and NSViewController respectively) are disparate from views and controllers in iOS (based on UIView and UIViewController respectively). This is mostly due to differences between the two platforms. It inevitably confines cross-platform reusable space to model classes. On the other hand, it is not very unlikely to have certain views in the product that are supposed to appear and respond to user events in similar ways in the two platforms. Failure to exploit this cleverly in the architecture can lead to code replication causing less maintainability. It will also disrupt the homogeneity in user interface semantics of the application between the two platforms. Thereby strict adherence to traditional MVC hinders the architect from harnessing the power of this domain artifact.

Embed Size (px):

14

Adapting View Models as a Means For Sharing User Interface Code Between OS X and iOS Dileepa Jayathilake SATURN 2013

Transcript

Page 1: Adapting View Models as a Means For Sharing User Interface Code Between OS X and iOS

Adapting View Models as a Means For Sharing User Interface Code Between OS X and iOS

Dileepa Jayathilake

SATURN 2013

Page 2: Adapting View Models as a Means For Sharing User Interface Code Between OS X and iOS

Background

Problem Identification

Solution Overview

Implementation

Discussion

Conclusion

OU

TLI

NE

Page 3: Adapting View Models as a Means For Sharing User Interface Code Between OS X and iOS

Product for both OS X and iOS

BACKGROUND

With a significant part in common

How to reuse code maximally?

Page 4: Adapting View Models as a Means For Sharing User Interface Code Between OS X and iOS

BACKGROUND

Page 5: Adapting View Models as a Means For Sharing User Interface Code Between OS X and iOS

PROBLE

M

IDENTI

FICAT

IONIs it possible

to share UI code?

Page 6: Adapting View Models as a Means For Sharing User Interface Code Between OS X and iOS

SOLUTI

ON

OVERVIEW

Page 7: Adapting View Models as a Means For Sharing User Interface Code Between OS X and iOS

View Models implement common part of UI

View Models are shared

View hooks into View Model

Controllers hold platform specifics SOLU

TION

OVERVIEW

Bidirectional bindings are platform-specific

Page 8: Adapting View Models as a Means For Sharing User Interface Code Between OS X and iOS

SOLUTI

ON

OVERVIEW

View Models contain view data and common UI behaviorModels are exposed to Views through View Models

1

2

Page 9: Adapting View Models as a Means For Sharing User Interface Code Between OS X and iOS

SOLUTI

ON

IMPL

EMENTATI

ON

Common & Platform-specific components of the solution

Page 10: Adapting View Models as a Means For Sharing User Interface Code Between OS X and iOS

SOLUTI

ON

IMPL

EMENTATI

ON

Proof of Concept: Book Store Application

Page 11: Adapting View Models as a Means For Sharing User Interface Code Between OS X and iOS

SOLUTI

ON

IMPL

EMENTATI

ON

Use of the solution in Book Store application

Page 12: Adapting View Models as a Means For Sharing User Interface Code Between OS X and iOS

Advantages

• Improved code reuse• Better readability• Better Separation of View Logic• Enhanced testability

Concerns

• Framework class usage• Bi-directional bindings

DISCUSSIO

N

Page 13: Adapting View Models as a Means For Sharing User Interface Code Between OS X and iOS

CONCLUSION

View Models combined with traditional MVC can improve code reuse significantly while providing other advantages for applications

targeting both OS X and iOS.

Page 14: Adapting View Models as a Means For Sharing User Interface Code Between OS X and iOS

QUESTIONS

Recommended

Strategic International Knowledge Sharing and …...Strategic International Knowledge Sharing and Communications Adapting to Climate Change in China • Developing countries are at

Adapting iOS 8 in iOS 7 Apps

#XamarinDevDays - Meetupfiles.meetup.com/16095872/Dev Days 2 - Xamarin.Forms.pdfTraditional Xamarin Approach With Xamarin.Forms: More code-sharing, all native iOS C# UI Android C#

Instagram iOS App in 44 minutes Photo Sharing on iOS

ap ecu.10N ap ê!SUOd ap fnqo TdO'O oo,10U ap esa.tpe 'atunN esans a!ios/ios as.ms !1d0D • £ 'L a!ios/ios . CL V aubu a!ios/ios ugp 9 alios/ios • CS .

Adapting the Landscape

News & Politics

site.judbrasov.ro · apmsed mppap as soŒ1 ap .10)uaaua a!ios/ios as.ms tup a!ios/ios 00.1011 ap auk) us.uns a!ios/ios • 79 ti!P '9 a!ios/ios a!ios/ios ti!P a!ios/ios .101!.munq

Adapting Consumer Report’s Product Evaluation Methods for ...ceisip.mit.edu/system/files/reports/Adapting Consumer Report’s... · Adapting Consumer Report’s Product Evaluation

RAD Studio XE4 - iOS Tutorials: Delphi iOS Application ...docs.embarcadero.com/products/rad_studio/radstudioXE4/iOS Tutorial... · iOS Tutorials: Delphi iOS Application Development

Creating and adapting teaching materials for sharing workshop 11_march2013_upload

iBGP Multipath Load Sharing - netadm.com.br Multipath... · iBGP Multipath Load Sharing Feature Overview 2 Cisco IOS Release 12.2(14)S Figure 1 Non-MPLS Topology with One Best Path

Rapidly Adapting Artificial Neural Networks for Autonomous ...papers.nips.cc/paper/432-rapidly-adapting-artificial-neural-networks... · Rapidly Adapting Artificial Neural Networks

EARLY INTERVENTION SESSION NOTE Adapting to Routines Sharing your Expertise Communicating and Collaborating.

User Privacy on iOS and OS X - Apple Developer · Family Sharing There will be an increased number of accounts belonging to children ... New and Updated Data Classes in iOS 8 Category

Page No.-1- Adapting Individualization Techniques For ... · Adapting Individualization Techniques For Large Classes . Page No.-2- Adapting Individualization Techniques For Large

Setting up Family Sharing iOS 13 and earlier

Sharing up to 80% code for iOS, Android, and Windows platforms, a Retail App Case Study, Roy Cornellisen and Marcel de Vries

Adapting Designs