Categories
Apple

The Apple Watch is just a watch

A wonderful bouquet of flowers.John Lilly [via Medium]: It is, fundamentally and essentially, just this: a wristwatch. If you’re someone who wants to wear a watch, this is a great one in many ways. If you’re someone who doesn’t want to wear a watch, this will not make your life better. In 2015, wearing a watch is a bit of an affectation — you have to want to have a watch on, you certainly don’t need one — and that’s true for this, too.

I don’t own an Apple Watch at the moment, but I probably will at some point because I will eventually have to write an app for the platform. Since its release I’ve thought long and hard about how I think I’d use it. I’m not a notifications guy. I only have a few on my phone, and I’d have fewer on my wrist; phone calls and text messages, but only from a select few. The one real benefit for me, and no I’m not joking, is the hope I miss fewer phone calls or text messages from my wife. Everything else the watch has to offer is fluff. 

What about the fitness stuff? I’m not sure this will work for me. I wear my watch loose on my wrist. It binds up otherwise. I tend to buy watches with link bracelets and I’ve broken everyone I’ve ever had, I don’t know how, but it happens. Hopefully the flubber sport band will keep that from happening, but I guess we’ll find out some day.

I will, of course, buy the least expensive 42mm model. The guts of the low end and high end models are the same, and the low end model is still ridiculously expensive at $349.00. I had the tiniest of hopes these things would run around $149.00, but Apple doesn’t do that. They can charge a premium and get it, so they do. I’m hoping this generation will drop in price dramatically once gen two ships. Hopefully it will be able to run version two of the OS. Call me a tightwad if you’d like, it’s a fair assessment. I have a hard time spending that kind of money on myself. 

Customization is something I’m really interested in. The only thing I’m hoping for as a developer is a watch face SDK. Apps are fine, but I want to customize the watch face. I could imagine having my Dumbledore watch face and I like the idea of it (yes, I own one of these watches.) Beyond that I have an idea some really brilliant designers will have fun creating watch faces. I could also see a one off market for rich people. Hey, if you spent thousands of dollars on a watch, you might spend thousands on an original work of art for your device, right?

Something else I really want to do is anodize the aluminum case. I have a hankering for a bright orange case with a custom built leather strap. This is the customization I desire above all others. I’m not sure I’ll be able to pull this one off given the hostile to fixers build of the watch.

There is one thing about the watch that really disappoints. I had high hopes Apple would make a timeless classic, instead they opted for a throwaway commodity. When I read about the System on a Chip (scroll down to read about the S1) they had designed for the watch I had imagined the ability to open the case and swap out the system with a new generation. It would appear, based on the iFixit tear down that Apple sees this device as a throwaway gadget. That’s kind of sad. A timeless classic would have been so much nicer, especially for the versions that cost over a thousand bucks. Real watch makers build timeless pieces. Apple has added the commodity thinking we have in tech. Just throw it away and buy the new one. I’m as guilty of this line of thinking as the next person. 

Apple will learn a lot from generation one. Eventually the watch could replace the phone as a primary communication device for text and voice. For now, it’s a 1.0 with nowhere to go but up. It’s off to a good start.

Update: After posting I ran across this tweet. I see more and more like this each day. I dont think this is a signal of the watches failure. It’s just the reality of it. It’s a nice watch.

https://twitter.com/marcoarment/status/599925897697824769

Another thing to note: I take reviews, like those at John Gruber’s excellent Daring Fireball, with a grain of salt. John makes his living from his support of Apple, and their products, and is never harsh. He finds the best in everything Apple does, and there is nothing wrong with that. I try to seek out neutral parties on the subject, which is hard to do. Most people either love or hate Apple. I felt like John Lilly’s comments were pretty neutral.

Categories
Apple

Used Apples

That Watch looks great on your wrist.9to5Mac: “Lee is a server at a restaurant. He considers himself a trendy guy and is looking for something that will look great while he’s working and when he’s out with friends. He’s interested in the Apple Watch collection and has narrowed his choices to these favorites:”

I love Apple. I feel I have to get that out of the way because I’m not happy seeing these personas, if they’re real (they may not be.) It’s obvious whoever created the Lee persona doesn’t have a clue how much a server at a restaurant makes. Lee may have great tastes, but his tastes outweigh his salary. Maybe Apple will have its own financing?

Here’s a guy that most likely makes less than $1000.00 a month and an Apple employee is going to encourage him to purchase the most expensive version of Apple Watch? This feels irresponsible.

I’m not sure how Apple Retail employees are trained. Maybe they’re taught to upsell every product in the store? “Hey, Bob, I think that 6 Plus looks swell in your gigantic man hands.” It could happen, right?

I’d love to hear from someone in Apple Retail. Does Apple train you to upsell the entire product line, or is this unique to the Watch?

Categories
Apple Life

A $349 Watch? You’re Rich.

Tech Crunch: “And that is the target market of the Apple Watch. Not “rich people” (though there’s a model specially for them), not “tech geeks” and not “Apple fanatics.” It’s people who want more time, and that is a very large target.”

Face it. If you can spend $349.00 on a watch, you are rich.

Categories
Apple Business

Crazy Prediction (A.K.A Wishful Thinking)

On occasion I think how interesting it would be if certain companies acquired other companies. Here’s one I’ve thought about quite often.

AHHHHHH!I’m a big fan of The Iconfactory. I use Twitterrific every day, as well as xScope. Both are beautifully designed products and easy to use. I’ve been thinking for a very long time, Apple should acquire The Iconfactory. Not just for their products, for their design and engineering talent. I think they would have to discontinue many of their products, like Twitterrific, or find a buyer for them, but xScope could be given away as part of the Xcode development suite and they will have gained a great design and engineering team. One that gets Apple.

Categories
Apple

AppKit is to the Windows API…

OMG NEW FRAMEWORK!

Will write C/C++ for foodThere was a lot of buzz generated around the discovery of a private framework, called UXKit, that shipped with Apple’s upcoming Photos for Mac app. Like many others I initially thought “It’s about time.” Then I started thinking about the transition that happened when Microsoft created C# and .Net. At the time we had the Windows API and our trusty C/C++ compiler. At the time .Net shipped in early 2002 we were still building desktop applications, the web was moving forward, but not at the pace it is today. Microsoft shipped WinForms, which was pretty much a straight wrapping of the Windows API’s for .Net developers. The point is, Microsoft gave developers a way to do stuff with the new language and runtime that could get them up and running quickly. The environment was different, but the API’s felt familiar.

Moving Forward

In 2006 Microsoft released a new framework called WPF (Windows Presentation Foundation.) This new framework made use of DirectX so rendering the user interface was hardware accelerated, along with other nifty stuff. As far as I know this was the last major framework Microsoft created for desktop developers. Since that time web development and Surface (Metro) seem to be their primary focus. (Someone please correct me here, if this is not accurate. I’m not that dialed in to Windows desktop API’s any longer.)

The point is, Microsoft went through this weird transition from the Windows API to a intermediate (WinForms) to their final desktop UI framework over the course of four years. Creating new technologies and frameworks is hard. They take time, but Microsoft is good at API’s, and they’re very good at maintaining them and providing developers an upgrade path. This is, I believe, where Apple is today. They’re in that awkward period between AppKit and whatever is next.

Enter Swift

In the summer of 2014 Apple gave developers a great surprise at WWDC. They introduced us to a new language; Swift. Since that time Apple has created a weblog dedicated to the language and shipped Xcode 6 with full Swift support. At this point in time it seems like Apple is pushing hard for iOS and Mac developers to adopt Swift as their primary development language. They seem to be “all in.”

Get to the point

Long story short. Do I believe UXKit is a future version of UIKit for Mac development? No, I don’t. I believe it’s a private framework created by the Photo’s team (or another team) to allow them to share a bunch of code with the iOS counterpart. It makes sense. Apple traditionally operates very lean. They have very small teams, so they need to work as fast and smart as they can. If they have a framework that allows them to share more code, it may allow them to move more quickly.

Ultimately I believe we will get an entirely new framework. Built from the ground up using Swift. I suspect that framework will aim to share code between iOS and Mac where it makes sense, and diverge where it doesn’t. The overall feel will be the same for both platforms. It will be unified.

I love thinking and writing about future technologies. I’m rarely ever right in my guesses (see my musings on WinRT), but it doesn’t stop me from dreaming.

Categories
Apple

Apple Austin?

t-gaap: “Would Apple be better served by augmenting the Austin campus to the point of moving Apple’s headquarters to Texas?”

No.

They would experience a brain drain never before seen in our industry. People love working for Apple, but they also love California. Even though I’ve heard nothing but great things about Austin, it’s pretty hard to beat what we have here.

Not to mention Apple’s green initiatives align with California values. Texas? Not so much.

Categories
Apple

Blah, blah, blah

CNBC [via Daring Fireball]: “They only have 60 days left to either come up with something or they will disappear,” said Trip Chowdhry, managing director at Global Equities Research.

Where do they find these guys? When I read stuff like this it’s obvious these analysts do not understand how Apple works. Someone made up the idea of the iWatch, a bunch of competitors in the market jumped on it, now Apple “must” have one? That’s definitely not how they work. They never have and I don’t see that changing. I’ know they’ve grown over the years but Apple runs very lean. They stay focused. Would I be surprised if they created some sort of wearable device? No, I would not. Would I be surprised if it was just a watch? Yes. Look, they already created the iWatch years ago(September 1, 2010) and didn’t know it.

Here is something else to think about. Apple wasn’t the first to create a computer, a music player, a smart phone, or a tablet. They just did it better than anyone before them and changed how we look at these devices.

Categories
Apple

Gruber and Simmons

RibbitI had a couple hours of driving to do today, had to take my busted computer in for repair. To while away the time on road trips I often listen to a podcast or two. Today’s selection was The Talk Show, Episode 75.

Messrs. Simmons and Gruber discussed scripting languages and asked if Apple needs to create a modern language for iOS and Mac development. The discussion was good, but I think there were a couple topics they could have touched on.

Pointers

Every C, C++, and Objective-C developer has had to deal with them. With the introduction of ARC a few years back pointers are all but an afterthought in Objective-C. Sure, there are exceptions, but mostly we no longer have to worry about freeing memory and it’s taken care of by the compiler, not a garbage collector. We have the best of both worlds with Cocoa and Objective-C; Native speed and memory management.

C#

Something they mentioned was Microsoft’s creation of a modern language based on a C lineage. It makes sense to do that because there is a big pool of developers that understand it, but I digress. I think the more important technology is Microsoft’s creating of the CLR and the .Net framework. One of the reasons these two items are so important is, they’re language agnostic. You don’t need to know C# to realize the full power of the CLR and the .Net frameworks. Take a look at CLI languages. It’s big. This gives developers the ability to use libraries from other developers and still work in their preferred language.

In the end I’m not so sure Apple needs to do anything. They’ve build, and continue to build, a great developer ecosystem. The Cocoa Framework is mature and is a huge benefit to iOS and Mac developers because we get a lot of shared code between the two.

Do we need scripting languages? Absolutely! Do we need them to build high performance native applications? Not really.

I’ve keep harping on this next point. Where we need advancement is in the browser. It’s locked in JavaScript hell. The browser is the new OS. The browser really needs a full CLI implementation.

If you have some time to kill download the episode. I really enjoyed it.

Categories
Apple Design Development iOS iPad iPhone

iOS 7 Lowers the Bar

iOS 7

A gift for you!If you’re an iPhone or iPad user Apple had a shiny new gift for you this week; iOS 7. I know, I know, it’s a bit of a jolt. I won’t lie. I hated it for a few days, but it’s beginning to grow on me. I’ve heard this time and again “Give it a few days.” I’ve given it a few days and it still seems a bit stark, but overall I’m happy with it. My trusty iPhone 4 seems much faster than it did with iOS 6. Bonus.

Benefit to Developers

I’ve written a few iOS apps over the last few years. Some have been lovingly designed by professional designers, others, like our own RxCalc were kept intentionally simple. Why? Truth be told Jay and I don’t possess the ability to make beautiful imagery for our app, so the design has to be simple. We developed our app using plain old UIKit, it works really well, is fast, and the binary is tiny.

With iOS 7 the bar has been lowered. A generic looking application looked fresh when iOS hit the streets. There were developers that created their own style and look, and, in turn, third party developers began to define the look of the OS, not Apple. Think about developers like Iconfactory, Tapbots, and Path. They all introduced applications that took the look and feel of applications way beyond standard UIKit, and that’s great. They stood on the shoulders of giants and moved the bar higher so the rest of the app ecosystem had something to reach for.

Third party developers created Pull to Refresh, the Hamburger and the Basement, and alternatives to UITabBar. All were very good innovations and gave us beautiful, very functional, applications. But there is a downside.

If you go against the Apple playbook, which isn’t a bad thing, you may end up creating something that doesn’t feel at home on a future release of an OS. Since iOS 7 shipped I’ve seen numerous folks comment about how outdated forward thinking and innovative applications like Tweetbot look.

I’m sure we’ll see an update for Tweetbot soon, but the point is, if your app has a completely custom UI it may take a lot of time and effort to make it look right in iOS 7.

Back to RxCalc and our choice to use UIKit, without custom design elements. Here’s how RxCalc looks on iOS 6 and prior, and it looks this what on iOS 7 before being recompiled:

RxCalc, UIKit for iOS 6 and older.

It’s not flashy, but it looks similar to Apple’s own Settings app, or Mail, on iOS 6.

Making an app new again

If you created a simple UIKit application your road to iOS 7 is simple. Most of the hard work has been done. You can recompile and your application looks new again.

Here’s what RxCalc looks likes when it’s recompiled with the iOS 7 SDK. No additional work, just a simple rebuild.

RxCalc, UIKit for iOS 6 and older.

Can it be spruced up a bet? Sure it can, but I can put this in the store today and it will look like it belongs.

That’s why I tweeted this a few days back:

It is super easy to get a fresh UI if you stuck to generic UIKit.

Reset

The bar has been reset, time for a new generation of user interface innovation.

Thanks, Apple.

Categories
Apple Development iOS

Apple Developer Center Breach

Full text of the email every registered Apple Developer received.

“Apple Developer Website Update

Last Thursday, an intruder attempted to secure personal information of our registered developers from our developer website. Sensitive personal information was encrypted and cannot be accessed, however, we have not been able to rule out the possibility that some developers’ names, mailing addresses, and/or email addresses may have been accessed. In the spirit of transparency, we want to inform you of the issue. We took the site down immediately on Thursday and have been working around the clock since then.

In order to prevent a security threat like this from happening again, we’re completely overhauling our developer systems, updating our server software, and rebuilding our entire database. We apologize for the significant inconvenience that our downtime has caused you and we expect to have the developer website up again soon.”

I know people love a good scandal, and being breached is a decent story, but nothing sensitive was compromised. It’s a major bummer they were hacked, but as far as the developer community is aware no app keys or credentials were stolen. No, our apps won’t have to be resigned and resubmitted.