Patterns and Practices for Scalable Apps

VideoYoutube Video - https://youtu.be/TQpRYibmyvQRelated EpisodesEpisode 39: Managing Code Quality with Anne CahalanEpisode 24: Continuous Integration with Kyle NewsomeEpisode 23: Modularizing in Xcode with Abbey JacksonEpisode 31: Future Proofing Your Apps with Gui RamboEpisode 15: Test-Driven Development with Joshua Greene and Michael KatzEpisode 14: iOS App Architecture with René Cacheaux and Josh BerlinRelated LinksiOS Continuous Integration: How To Avoid Merge HellSwiftUI: Everything is possible if you think like AppleHow to avoid iOS app failure with Test-Driven DevelopmentSwift Package Continuous Integration GuideSponsorsBrightDigitSpecialize in helping businesses build apps for iPhone, iPad, Mac and Apple Watch10 years of experience developing for a variety of Apple platformHelping dev shops which lack experience with Apple platforms and SwiftContact me if you need help today.We have an opening for sponsorsDo you have a product or service which can target our ever growing community of developers as well as technology and business leaders? Contact me today if you are interested in sponsoring or go to our Patreon page.Why Good Patterns and Practices MatterBug fixes and code upgrades become more difficult to executeAdding new features can be a real challenge if there's a lack of organization.Without breaking each layer and functionality apart, it makes testing excruciating.Without consistency, new developers will have a hard time understanding how the code works.By using the right patterns, modularizing your code, and maintaining good code quality; you can keep your app development project running smoothly and save money in the long run.Architectural PatternsUnderstand the legacy of Objective-CHow Model View Controller is intrinsic to UIKit  How do Delegation Pattern fits Why Protocol Oriented Programming works so well with Swift and Testing?Why Functional Programming makes it easier to build complex functionality?Why the shift to Model-View-ViewModel?How Reactive Programming, the Subscriber-Publisher model, and Combine makes sense for UI development?Modularizing Layers of FunctionalityModularity ensures individual pieces of functionality can work independently. While each piece of code and functionality remains simple, it is their multitude and integration which is complex.Each module is an Interchangeable Part.Modularity allows for use in multiple operating systems and devices.How does Xcode and Swift allow for modularityWhy Framework Targets are the most mature way still to create independent Where Workspaces and Projects fit with with Independent Apps and ProductsWhy Swift Packages are the futureMaintaining Quality CodeGood Architectural Patterns means Easy TestingCode Coverage is a good metric but not the only one.Reduce Complexity in your code for easier maintenanceConsistent Styling makes version control and team management easierCode Reviews Help get an additional set of eyes even though they may be your own.Continuous Integration of components and apps are the best way to ensure quality codeSocial [email protected] BrightDigit - @brightdigitLeo - @leogdionLinkedInBrightDigitLeoInstagram - @brightdigitPatreon - empowerappshowCreditsMusic from https://filmmusic.io"Blippy Trance" by Kevin MacLeod (https://incompetech.com)License: CC BY (http://creativecommons.org/licenses/by/4.0/) Thanks to our monthly supporters Steven Lipton ★ Support this podcast on Patreon ★

There are no comments yet.

Please log in to write the first comment.