I haven't done any iOS development before but is there any real reason why a tiny app with what seems to be ~100 lines of code needs to be split into several small files with even fewer lines in them?

https://github.com/WDUK/A9ChipSource/tree/master/A9ChipSourc...

As far as I can see, the actual work is performed by around 5 lines of code in this file, which reads a configuration value, performs two string comparisons, and outputs to 2 text fields:

https://github.com/WDUK/A9ChipSource/blob/master/A9ChipSourc...

In other words, is this level of verbosity/"fluff" typical of iOS apps?

That's not much verbosity/fluff. It's the typical default auto-generated code files; basically the author said "new project" and filled in a few lines. No need to hand-optimize this into minimum files.

ETA: With some cut-and-paste & removing stubs, and preserving the storyboards, the whole thing can be reduced to 20 lines in just main.m, smaller if you shift into "obfuscated objective-c" mode.

A quick port to Swift: https://github.com/mnem/SwiftA9ChipSource. The functional bit is in https://github.com/WDUK/A9ChipSource/blob/master/A9ChipSourc....

Objective-C isn't too bad. I've certainly had more boilerplate to deal with on various other platforms. In terms of names, it is verbose though. It's one of the things I really like about it.

How do you do this in Swift?

CFStringRef val = (CFStringRef)MGCopyAnswer(CFSTR("HardwarePlatform"));

NSString* chipIdentifier =(__bridge NSString * _Nullable)(val);

Theoretically just:

let u = MGCopyAnswer("HardwarePlatform")

However, the problem is that MGCopyAnswer is a private method, and thus you have to define an interface for it. You can't do that in Swift, however you can do it by creating a bridging header for Swift.

So you'd need to add a bridging-header.h to the project, then set the compile target up to use the bridging header, and finally add this to the bridging header:

#include <CoreFoundation/CoreFoundation.h> #if __cplusplus extern "C" { #endif CFPropertyListRef MGCopyAnswer(CFStringRef property); #if __cplusplus } #endif

That's not correct. You can define it with @asmname.

I hope this code finds way into mainstream system information apps on App Store.

Why would I care where the processor in my phone is made?

Please pardon my ignorance...

My impression was that only apple approved, app-store delivered software could run on iPhone/iPad/iWhatever ...

Am I wrong to be surprised to see an "iOS utility" hosted on github ? What am I missing here ?

iOS apps can be built/signed/installed from a Mac running Xcode 7 without any extra requirements. I'm surprised this fact hasn't gotten more press.

Now this is interesting, had to dig it out:

Free On-Device Development

Now everyone can run and test their own app on a device—for free. You can run and debug your own creations on a Mac, iPhone, iPad, iPod touch, or Apple Watch without any fees, and no programs to join. All you need to do is enter your free Apple ID into Xcode. You can even use the same Apple ID you already use for the App Store or iTunes. Once you’ve perfected your app the Apple Developer Program can help you get it on the App Store.

See Launching Your App on Devices for detailed information about installing and running on devices.

( From the feature list for xcode 7 — https://developer.apple.com/library/prerelease/ios/documenta... )

My theory was that the whole developer key thing was a very effective piracy countermeasure — registering and paying $100/year (iirc) is expensive and inconvenient enough that it's easier to just buy things. What has changed?

How did he know what manufacturers those ids mapped to?

https://github.com/WDUK/A9ChipSource/blob/master/A9ChipSourc...