Posts tagged "apple"
I’ve got a bag of accessories that I cart around that meets about 95% of all the tech needs I tend to have these days, but there’s one accessory I’ve wanted in there that doesn’t exist: the perfect Apple Watch charger.
I love to browse through Github and see the sorts of frameworks people build. Pretty frequently I come across repositories that make a good effort to provide a cross-platform experience by offering iOS, watchOS, and tvOS versions. Sometimes there’ll even be the odd macOS version too!
In my conversations with developers, I’ve heard a pretty common theme from them that “Core Data is hard” or “Core Data is buggy” or “I could never get it to work right and gave up on it”.
About five months ago, I wrote about improving MVC and fixing the “massive view controller” problem.
I bought my kids (6 & 8) their own iPads last fall. I’m nice, and I’m fortunate to be able to afford it. However, I’ve come to realize that despite my attempts to spoil my kids, these iPads (and all iOS devices in general) are not meant for kids.
Recently Quinn, an engineer on the Developer Technical Support team at Apple, posted a request for feedback on Apple’s networking APIs. Here are his questions and my answers:
If I were Supreme Swift Potentate, there are a few things I’d change about how Swift deals with protocols, and how this gets manifest in the standard library.
I’ve developed a handy trick when writing frameworks in Swift that makes the overall process a little bit nicer, and it’s just adding a single file to your framework.
When you’re writing an iOS or macOS app, you typically don’t need to dynamically know what your own entitlements are. However, there are a couple of rare circumstances when it could be Nice To Have.
There are other ways you can apply these principles to writing more maintainable apps.
The principle behind fixing Massive View Controller is to unlearn a concept that’s inadvertently drilled in to new developers’ heads:
In order to fix the encapsulation violation we saw earlier, we need to understand a pretty simple principle:
I recently ran across a great article by @radiantav called “Much ado about iOS architecture”. It addresses a topic that has been on my mind a lot. I gave a talk about it at the recent Swift by Northwest called “A Better MVC”. These blog posts attempt to capture the main points of my talk.
So, I love Keynote.app. It’s one of my all-time favorite apps. During my time at Apple, I got to use the app a lot and was constantly amazed by how powerful and capable it is. I grew very used to its precision and elegance, and its overall ease-of-use.
For a while now, there’s been a major feature of iOS Contacts that I’ve felt has been sorely lacking, and that’s the ability for third-parties to provide their own contact card data. Here’s what I mean…
It seems like it was only the other day when I wrote the post about leaving the Evangelism team.
Several months ago, our family decided to make a drastic change. After nearly five years living in the Bay Area, we decided it was time for us to leave. The exact reasons for this are somewhat lengthy and personal, but they boil down to two main things: Housing prices and proximity to family.
(This was originally posted in April of 2009 and has been reposted here for posterity)