Apple revealed new iPhone X on their last September event, which comes with a brave new design. The device is no longer rectangular and it has rounded corners instead, edge-to-edge display, and a notch on top of the screen which holds camera and sensors for new Face ID. It also lost the iconic home button, and it has been replaced by a virtual home indicator. The question is how will current apps behave on new iPhone X, and how can you adjust your apps for it?
If you’ve had a chance to try out the new Codable protocols recently made available in Xcode 9, you may have noticed that they’re not exactly flexible in the way your previous JSON library might have been. The new JSONDecoder that is provided with the Swift standard library is a bit of a control freak, but with a little bit of protocol extension, we can fix that.
iOS 11 introduced a huge range of changes that are already revolutionizing app development, not least Core ML, ARKit, drag and drop, and more. Following that epic release, the first beta of iOS 11.1 was released and so far mainly seems to be a few small tweaks to APIs that got missed off the initial iOS 11.0 release.
Every language has their own rules. It does not matter if you look at the syntax, language features or type of language. Everything changes and at the same time it stays the same. In our themed app we will be using swift, but since Objective-C is the origin of iOS development, we make a little detour, to see how specifics are done here.
Using remote images in an application is more or less a requirement these days. This process should be easy, straight-forward and hassle-free, and with Imaginary, it is. The library comes with a narrow yet flexible public API and a bunch of built-in unicorny features.
Does your iOS app have access to the user's image library? Do you want to know your user's movements over the last several years, including what cities they've visited, which iPhones they've owned and how they travel? Do you want all of that data in less a second? Then this project is for you!
detect.location is not intended to be used in production. It's a proof of concept to highlight a privacy loophole that can be abused by iOS apps. Apps shouldn't use this. The goal is to close this loophole and give its users better privacy controls for image metadata.