This year’s WWDC was full of surprises for developers. Apple chose the path of opening so many aspects of iOS to developers, which is something that we could not even think of some years ago. Users download more and more apps and spend more and more time on their smartphones. Apple aims to help this by eliminating the number of times users have to open apps and find what they want.
Array is one of the most used collection types in Swift. Although it is extremely powerful (and the language provides much faster array iterations compared to Objective-C) it lacks many of the capabilities we were used to when working with NSArray and NSMutableArray collection types.
Following last year’s post about my expectations for WWDC14, this year I am going to write a similar article about what I would like to see from Apple in WWDC15. Last year’s conference was a great one for Apple Dev community. We saw many great frameworks like CloudKit, HomeKit, HealthKit, extensions and an entirely new programming language, Swift.
After months of beta releases, the final version of Xcode 6.2 is here. Xcode 6.2 includes the SDK for the much anticipated Apple Watch. In this tutorial we will see how to create a WatchKit app that fetches data from the network and displays a simple table and a detail view. Tables in WatchKit work a little bit different than Table Views on iPhone.
One of the most popular posts in my blog is the tutorial for creating a Pop-up window with iOS SDK using Objective-C. Since then many readers reached me out asking for a Swift version of the Pop-up. In general the process is exactly the same in Swift (except the language used to write the code of course…), so I am not going to dive into the process of creating the .xib files again.
Over the years, iOS developers have used various tools in order to record screencasts for their apps. Starting with OS X Yosemite this process became much easier. Using the built-in Quicktime app in iOS Yosemite, we can now easily record our iPhone’s or iPad screen. The steps are pretty straightforward.
As almost all Apple developers, I was excited with the announcements Apple made in WWDC this year. Lots of new stuff, a revamped OS X experience, a new iOS version with refinements for the end user and great new APIs for developers and a whole new programming language: Swift. Last year Apple completely redesigned its mobile operating system, leading to a lot of criticism, although most reviews where positive. iOS 7 was new and fresh but in many ways it seemed like an unfinished product.
In WWDC 2013, Apple introduced Xcode 5 and iOS SDK 7 with a built in framework for testing: XCTest.framework. Unfortunately Apple documentation lacks details for this framework. In this post I am going to present a simple way to test a UITableView using XCTest framework.
In an iOS project I am currently working on, I got a request to create a pop-up window. Trying to figure out how to do it, I came up with a solution that is pretty easy to implement and very straight forward. All you need is a view controller with a transparent background and a subview (your popup window). After creating the popUpViewController, you can just call it from any other view controller.
Last year at WWDC 2012, Apple introduced Modern Objective-C alongside iOS 6. So what’s this? In a few words, it is a huge step forward to help developers write less code to achieve the same things. Worth mentioning is that modern Objective-C has nothing to do with iOS versions, it has to do with the compiler, which means that it is backward compatible.
Let’s dive into the basics of transitioning to modern Objective-C. Xcode offers a refactoring tool (edit>Refactor>Convert to Modern Objective-C syntax) which will convert your project to modern objective-c (it will also set the appropriate flag in build settings). If you would like to adopt modern Objective-C when writing your code, which is the best, as it is intended to help you write less lines of code, general rules for doing so are the following.