Handoff is a neat feature that was introduced in iOS 8 and macOS (then OS X) v10.10. This capability allows an app to pass data across macOS and iOS devices so that a task started on one device can be completed on another device. The difference between this and continuing an activity by saving a file to a place like iCloud and resuming the activity on another device is context. Meaning that when you use handoff, unlike other methods, the user of your app will be in the exact same location, when the app is opened on a second device, as they were on the first device.
At WWDC Apple announced that iOS 11 will now support Drag and Drop. This works not only within an app, but also from one app to another. Dragging between apps is only supported on iPads. Drag and Drop between apps works if the iPad is in split view mode, with both the source and destination apps open side by side, or even if the destination app is completely closed.
If you have played with iOS 11 either on a simulator or on a real device, you have probably noticed that most of the first party apps, such as Mail and Settings, use large titles in the navigation bar. We are going to look at how to implement the same navigation bar behavior in our apps. Unsurprisingly, Apple has made this very easy for us.
The debate as to whether or not the iPad can replace a computer is on going. We do not need to get into the discussion of who this might work for or what kind of work can be done with an iPad. The fact is that for some people this is already happening. Even if people are not using the iPad as a computer replacement, many people are at least using it as a light weight computer. It is a computer that has a pointing device (finger, Apple Pencil or stylus), a spacious screen and a keyboard, which allows us to use shortcuts.
CalendarKit is an open source project we have been working on to insert a calendar in an iOS app. There are many calendar frameworks that can be used but when we needed one they all seemed to be missing something that was important to us. As of June 2, 2016 we have implemented all of the features that we need. However, if you have a request for a feature let us know. We want to make this the best calendar framework there is.
The code can be found on GitHub and can be added to your project as source code or compiled into a framework.
Completely customizable UI – Font, color, placement of UI elements – EVERYTHING.
Set a minimum and maximum date – The calendar will never scroll beyond those dates.
Set disabled dates – In some applications special dates such as holidays should be disabled.
Set disabled weekends – A quick way to disable all weekends.
Accessory views – Need some way to indicate there is data related to a particular date? Use the accessory view!
Usable wherever needed – Full screen? Embedded in a larger screen? In a popover? This calendar can do it all.
For sample code on how to best use CalendarKit, checkout the GitHub page. There is a sample app in the same project where I have demonstrated a lot of the flexibility of the framework.
If you want to get started quickly all you need is this code:
If you have been using Swift over the past few months, chances are you have come across issues using Strings. Many of the Objective-C methods we have relied on no longer work without some extra leg work. Over the last few days I have seen several questions posed on blogs and forums asking how to complete certain tasks with Swift’s Strings. Some of the answers I have seen work, but really aren’t the best answers. Here is, in my opinion, the best way to handle a few of the scenarios I have seen multiple times.
These days every company is looking to “go mobile” but what if time, cost, or personnel do not allow for your company to have a full mobile app? Here we will talk about some ways to achieve the goal of “going mobile” without creating a dedicated mobile app.