Welcome to AppCoda Weekly Issue #4! I was just back from a short vacation. And this is the first time I travel with the new AirPods. While you may not agree with me, I really love this Apple product, and agree what M.G. said in this review, “This is exactly the product I’ve wanted for years. Apple nailed it.”
Pairing and switching between different Apple devices are so easy and seamless. My only complaint is about the battery. I’m not talking about the battery of AirPods. But it is about the battery drain issue of my iPhone 6s Plus while using the AirPods. I didn’t use to carry a battery pack, but now I have to. Earlier, Apple released the first firmware update of AirPods. Hopefully it can resolve the bug. Scroll down and check out the article if you also experience the issue.
This week, we continue to bring you quite a number of tutorials for your weekend reading. Some of them are related to debugging, and some of them are related to design. Just pick the one you like and keep learning!
Having to incorporate the design iterations (Read: icon colors, backgrounds, etc.) at the last minute can be a developer’s as well as a designer’s nightmare. This is especially true if the size of the app is bigger and so is the style code. So if there a way to control all of this code from one place? Really?
Table views and collection views are both designed to support displaying sets of data that can be scrolled. However, when displaying a very large amount of data, it could be very tricky to achieve a perfectly smooth scrolling. This is not ideal because it negatively affects the user experience.
One of the top priorities for Swift right now is compatibility across future Swift versions. This document is an exploration and explanation of Swift’s ABI alongside the goals and investigations needed before declaring Swift’s ABI stable. It is meant to be a resource to the community as well as a declaration of the direction of Swift’s ABI.
Memory leaks start as an irritant but if not taken care of quicly, they can pop up everywhere and jeopardize the entire code. So what makes them happen, when, and which tools can help eliminate them. Find out.
Xcode projects that mix Objective-C and Swift cause the Swift compiler to take longer processing times. What is the cost of such high processing times and how does Swift 3.1 address this issue? Check out this post.
Tracing the memory leak to the exact piece or line of code can be time consuming and painful. Now there’s something known as Malloc Stack Logging that helps the debugger find the exact lines of code causing the leak.
The next time you take a walk outside, try to become aware of the thousands of design decisions that were made around you. What works, and what can be improved? Can you discover designs that you haven’t noticed before because of how well they worked?
The upcoming iOS 10.3 will allow developers to prompt their users with an Apple system prompt without having to leave the in-app experience. It’s time to rethink how you prompt users to review your apps.