Just drop your icon onto the page, select which versions you want (iOS, Android, macOS, etc.), and click the “Generate” button. Nifty!
In the search for a comfy and portable developer experience, I’ve made a lot of compromises in the past. The experience has gotten significantly better recently thanks to VS Code and Kubernetes. This workflow also does a good job for underpowered laptops or when working with lots of different and conflicting versions of python or ruby.
This is a solid, balanced piece that doesn’t overly sell the workflow and walks you through setting it up for yourself.
This is the 2nd biggest piece of news coming out of the WWDC keynote yesterday, but you may have missed it (I did) because it was merely mentioned in one of those overview slides.
(The 1st biggest news was the ARM transition, but nobody missed that one.)
Brent Simmons did some analysis on download numbers for NetNewsWire on iOS and Mac.
Based on the above, and knowing that way more people use iOS than macOS, you’d expect the iOS app to be way more popular. But it’s not. It’s a little more popular.
I find this super-fascinating, because it’s some data — admittedly just one app — that confirms what I’ve thought for a long time, which is that, for some types of apps, a Mac app would do as well as an iOS app.
A complete iOS redesign of two pages in 10 minutes. Covers typography, iOS guidelines, “dark mode” theming, consistency, and more.
This is a full-featured virtual machine host for 30+ processors including
Erik Kennedy is back with an awesome resource for anyone doing iOS development.
Maybe you’ve never designed an iPhone app, and have no idea where to begin.
Maybe you’ve designed a dozen, but still want one place to reference best practices. Heaven knows Apple’s Human Interface Guidelines are awful to try and read.
Either way, this is the guide for you. I cover basically everything you need to know to create an iOS app that follows standard iOS 13 conventions.
iOS 13’s rollout was soooo buggy. Most notably: backgrounded apps were routinely being killed for no reason. What was to blame?
…Apple top executives Craig Federighi and Stacey Lysik identified iOS daily builds’ instability as the main culprit for iOS 13 bugs. In short, Apple developers were pushing too many unfinished or buggy features to the daily builds. Since new features were active by default, independently of their maturity level, testers had a hard time to actually use their devices, which caused Apple’s buggy releases.
Here’s how they plan to address the problem:
Federighi suggested leaving all new features disabled by default, so testers can ensure no regressions make it into the latest build and avoid being impaired by new bugs. New features shall be enabled on-demand by testers using a new internal Flags menu, making it possible to test each new feature in isolation.
How did it take Apple to the end of 2019 before they discovered feature flags? I hope it helps 🤞
From Erik Kennedy who shared some tactical design advice for developers — this awesome visual guide covers the primary differences between designing for iOS and Android, including navigation, UI controls, typography, app icons, and more.
If you’re designing both an iOS and an Android (Material Design) version of an app, this guide is your new best friend 😎. We’re going to cover the most relevant differences between iOS and Android for UX/UI designers. If you’ve created an app on one platform, this is most of what you need to know to “translate” it for the other platform.
Just fork the repo, configure and customize, then push it back up for GitHub Pages.
Today, I’m excited to announce updates to our guides to Swift Codable and Numbers, as well as a brand new Guide to Swift Strings. Everything is up-to-date with the latest from Swift 5 and Xcode 10.2, and now — for the first time — available in print!
What’s cool about this is it’s not a proxy, so you don’t have to futz with certificates, proxy settings, and the like. As long as the iOS device and your Mac are on the same local network, you can view the network traffic of your apps.
Federico Viticci on MacStories didn’t understand why Apple Music doesn’t offer a “Year in Review” feature, so he built his own:
But Apple doesn’t seem interested in adding this feature to Apple Music, so I decided to build my own using Shortcuts. The result is the most complex shortcut I’ve ever created comprising over 540 actions.
I just tried out the shortcut last night, and it’s incredible. But as Federico himself points out, doing something this complex pushes the boundaries of Shortcuts and iOS:
Apple Music Wrapped pushes the limits of what is possible to achieve with the ‘Find Music Where…’ and ‘Open URLs’ actions of the Shortcuts app. In the past few weeks, I (and other testers) have run into limitations and inconsistencies worth pointing out both for MacStories readers and Shortcuts engineers at Apple.
It’s nothing short of a programmatic feat, and if you use Apple Music, I recommend you give it a shot.
Mattt over at NSHipster explains two important abstractions on Apple platforms: bundles and packages.
Despite being distinct concepts, the terms “bundle” and “package” are frequently used interchangeably. Part of this is undoubtedly due to their similar names, but perhaps the main source of confusion is that many bundles just so happen to be packages (and vice versa).
So before we go any further, let’s define our terminology: …
Whether you are writing yet another one task tracker or calendar app, or simply want to offer the users to skip the joy of using
UIDatePickerand let them quickly and efficiently select dates — CrispyCalendar is the calendar UI framework you need.
Oh, yeah, for some reason I get a lot of questions like “Why isn’t Mastodon on the app store?” and it’s really weird, because there are like a million apps for Mastodon on every app store… They’re just not called Mastodon, because they are developed by third-party developers.
Mastodon has a principle - API first, and… Yeah, that’s essentially it - API first. [laughter]
Add Mast to the ever-growing list of third-party developers making iOS apps for Mastodon.
If this book intrigues you (like it does me), start nowhere else but the “How to Read This Book”:
A successful iOS game makes $4,000 annually (this goes for any app frankly). A successful Android game makes one seventh of that (one third at best).
You are not a large multi-million dollar company (at least I don’t think you are given that you’re reading this book). So you don’t have the customer acquisition/marketing budget to beat this $4,000 annual average. Period.
Brutal. What’s a dev to do, then? Make lots of niche, high quality games.
Unit testing and the tests themselves are written by humans. Humans are prone to error. Unit tests and the testing infrastructure can be imperfect. The
test_centerplugin includes tools that remove (or alleviate) the effects of an imperfect test infrastructure.
(fastlane is a popular way to automate building/releasing iOS and Android apps.)
Want developers of great software to be able to make a living doing it? Want free trials in the App Store? Join The Developers Union!
Dear Apple, We believe that people who create great software should be able to make a living doing it. So we created The Developers Union to advocate for sustainability in the App Store.
Today, we are asking Apple to publicly commit — by the tenth anniversary of the App Store this July — to allowing free trials for all apps in the App Stores before July 2019. After that, we’ll start advocating for a more reasonable revenue cut and other community-driven, developer-friendly changes.
Feeling nostalgic for Windows 95? Blake Tsuzaki was:
This is a little exploration into applying ’90s-era design & principles into a modern platform with some primitive components. The assets and design metrics were (for the most part) taken from an actual installation of Windows 95.
You may be wondering why all the effort? You’ll find answers to that question and more in the README.
Peder Norrby created TheParallaxView, a UI experiment for his iPhone X, that gives it a trompe-l’oeil effect.
Trompe-l’oeil is an age-old trick used by painters to create the illusion of 3D depth on a 2D plane. On the iPhone X, it’s downright mesmerizing.
The touchscreen itself seems to melt away as the phone transforms into a portal to an infinite abyss. Angle the phone, or your own head, and you can even peek inside, as if you’re looking through a peephole into another room, or inspecting a can of Pringles for the last few crumbs.
This is being called “the biggest leak in history”, which is probably not true (remember when Gizmodo got its grubby paws on the iPhone 4?). But it’s likely the biggest leak in Apple software history. Motherboard says it…
could pave the way for hackers and security researchers to find vulnerabilities in iOS and make iPhone jailbreaks easier to achieve.
That’s plausible. iBoot is responsible for ensuring a trusted boot of the O/S. The specific version posted was from iOS 9, but this portion of code probably doesn’t get updated as often as the Music app, so it’s likely still relevant.
Apple promptly posted a DMCA takedown request, and the source code is no longer publicly available. But we developers know all to well that once source code is made public, there’s no taking it private again.
This article isn’t a how-to, per se. It’s more like a research report written after attempting to build such an app for the first time. There’s nothing wrong with that, though, and this write-up is super useful if you’re about to tackle a similar problem space.
Open source libraries are tried, facial recognition services are evaluated, and their takeaways are solid, if not a bit disappointing.
As you can see, the really simple idea of using facial recognition functionality was not that simple to implement.
The entire piece is worth a read.
Bender allows you to easily define and run neural networks on your iOS apps, it uses Apple’s MetalPerformanceShaders under the hood.
Click through for some examples and an explanation of why they don’t use CoreML.
Time will tell whether they're too late to the game or not. In the meantime, the source code is freely available (and under heavy development). From the README:
This is a work in progress on some early ideas. Don't get too attached to this code. Tomorrow everything will be different.
Could be a fun project to track, especially if you're interested in Swift.