Writing high-quality Swift code requires discipline in applying good naming conventions, maintaining a clear separation of concerns (SoC), following the five principles of SOLID design (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion), and ensuring maintainability through best practices. While AI-generated code can be useful, it must be refactored and reviewed for clarity and correctness.
Swift – Apple’s slick and safety-focused (? still not sure I’m bought in on that phrasing) programming language – has become the backbone of Apple’s development. Whether you’re hacking on an indie app or shipping production-grade enterprise software, writing consistent, readable, and idiomatic Swift is non-negotiable. Swift has a robust set of guidelines to follow, and I wrote a thing or three about it’s style of OOP, POP, and FP rolled into one language here, but let’s cut through the noise and hit the key conventions that will level up your Swift code.
Swift is a versatile toolkit that lets you solve problems in multiple ways. Whether you’re leveraging the familiar object-oriented principles, diving into Swift’s protocol-oriented magic, or harnessing the power of functional programming, Swift has you covered. In my latest swift dive I’ve put together a break down of these paradigms per Swift usage.
This past weekend I attempted to get started with Swift coding. Since I have not been an Apple Developer for a while, it wasn’t immediately obvious how to get started. But once I fumbled around a few minutes I realized I needed a developer account to get the latest XCode. Jeez, it really shows how much Apple loves to lock you in hard core to their development ecosystem. An unfortunate trait of a company that is actually extremely closed in much of its behavior, while taking advantage of so much of the open source community. But I digress, this isn’t a rant about the unethical behavior of Apple. I’ll reserve that for the novels worth of material it deserves.
One I signed up for the developer program, which costs $99 bucks, I immediately made my first huge mistake. This damnable mistake blew the entire weekend of hacking. I added under “Company” my simple DBA (Doing Business As) name. I already had an account, and because of this change for making this existing account become a developer account from a personal base level account, sprung a red flag. I checked back frequently over the weekend, but it wasn’t until Monday that somebody checked the app, realized the Company name I added was merely a DBA and ok’d my account. So far, 38 hours down the drain for getting started hacking on Swift! Dammit.
However, this morning I was happy to find everything was ok’d, and thus, the remaining bit of this blog entry is a bit more example and a little less story of my day.
Developer @ Apple
Getting XCode 6 beta
I wanted to do Swift hacking, the first step was to download XCode 6 beta. That’s available via download on the iOS Developer page (and I suppose the Mac Developer page). Scroll down on that page until you find the XCode Download button.
The Warnings and the Download XCode 6 beta page.
Also note, if you’re looking to do Swift hacking like I’m doing here, I’d actually advise against getting the iOS 8 beta or OS-X Yosemite Developer Previews right now. Best to keep as stable a machine while toying around with a new language. At least, that’s what the conversations have been so far…
OS-X Yosemite & iOS 8
Once I got Xcode 6 beta installed I dove right into creating a Swift Project. I created a simple new project that is empty to just check out what Xcode 6 provides out of box for the Swift Project.
Selecting an empty Xcode 6 beta project to use with Swift.
The next dialog is where the Swift magic is selected.
Selecting Swift, entering a project name and other information dialog.
After that I just clicked through on defaults until I got into the Xcode IDE with the project open.
Selecting the appropriate simulator.
Next I executed the project. Since I’d had my phone attached it wanted to run it there, but I have 7.1 iOS on it which won’t execute Swift code. I had to select the appropriate simulator then to run the application project. Once that ran, since I’d not done so on this particular computer, I needed to enable developer mode.
Enabling developer mode.
I did so and the empty application launched.
An empty iOS 8 iPad Retina Application.
So that’s the basic getting started, no code actually slung. But rest assured I’ll have another post soon detailing some first code snippets. I also hope to get some comparisons written up between XCode with Swift and Xamarin Studio and C#. It’s cool that Apple finally has a modern feature rich language, so it’ll be interesting to see how each stacks up from a language and IDE perspective.
You must be logged in to post a comment.