[{"_1":2,"_46":-5,"_47":-5},"loaderData",{"_3":4,"_14":15,"_44":-5,"_45":-5},"root",{"_5":-5,"_6":-5,"_7":-5,"_8":9,"_10":11},"user","shoppingCartId","toast","locale","en","constants",{"_12":13},"paypalClientId","AenrHU49peF-ZUH-Yq7AXLLNZYGUGlml474U16NCjB4ZznmQCEjiliN3whyuVZmkb7VxEzmTALgtKEKE","routes/_store+/_readers+/email_author.$slug/route",{"_16":17,"_43":-5},"book",{"_18":19,"_20":21,"_22":23,"_24":25,"_26":27,"_28":29},"id","Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6Qm9va1Byb2R1Y3QvMTQ3NTY","title","Exploring Mac App Development Strategies","state","published","contactAuthorMethod","email","aboutText","

Driven by Example, this Book Applies Useful Patterns of Clean Software Architecture to Mac App Development

You do some kind or other of what may be called \"software architecture\" anyway.

So better know the reasons for the moves you take. Own the alternatives, and design your code accordingly to gain confidence that your stuff is really working.

Learn how to …

design reusable code,
get a solid test harness up and running, and
separate the components of your application.

All this will make your application easier to change and easier to maintain. It will make you a happier developer, even when you're just exploring new parts of the Cocoa Framework.

To develop Mac applications, you'll need to know why and how to separate components. Using the latest technology and a head-start into Swift programming, this book will show you the pro's and con's of several design decisions and discuss alternative approaches so you get to know your options.

The Core Ideas of the Book

I want to share the core ideas and theses of the book with you:

Apple's Core Data is a very invasive framework. It works best when you couple everything, beginning at the user interface, to Core Data entities. Cocoa Bindings make a lot of the magic possible, but they come at a cost: the Core Data entities (or NSManagedObject subclasses, for that matter) are bound to do a lot of different things for different \"clients\", wheras by 'client' I mean consuming views, background services, and the like. It'd be easier to maintain the code if you model entities for each \"Bounded Context\" separately.
Adopting Domain-Driven Design thinking, small service objects are favorable. It's easy to create Data Transfor Objects in Swift using structs, for example. Core Data should be pushed outside the domain (i.e. where the business logic is hosted) and become an implementation detail.
Once you free your app from the entanglement by Core Data (and other Apple suggested best practices which don't scale well), you will be able to leverage powerful design patterns. I created domain event wrappers around NSNotification to make event handling easier and failure-proof. Using events to propagate changes (instead of using Bindings, for example) makes concurrent programming easier.

That's part of the topics we cover in this book. Maybe you won't be a DDD expert afterwards, but so neither am I. Instead, we'll explore useful patterns to make the code manageable and to get more comfortable ever writing Mac applications which are ready to scale.

The Book is Open Source, by the way!

The book is Open Source. You can contribute on GitHub:

\nBook manuscript and manuscript website\n
Example project code

Just create a pull request if you came up with a better description of something, or if you want to add a useful reference, for example. Together, we can make the book a lot better.

Your feedback is much appreciated!

","authors",[30],{"_18":31,"_32":33,"_5":34},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci8xNTM4NA","name","Christian Tietze",{"_35":36},"avatar",{"_37":38,"_39":40,"_41":42},"url","https://d308did4coypzi.cloudfront.net/avatars/208411/medium/ausgewaehlt-xing_sm.jpg?1596871725","styleName","medium","exists",true,"currentUser","routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

Email the Author