Warning: preg_replace(): Compilation failed: invalid range in character class at offset 4 in /home/happymaa/public_html/coderchrismills.com/wp-content/plugins/crayon-syntax-highlighter/crayon_langs.class.php on line 340
Dandelion Breeze – Now Available – Chris Mills Press "Enter" to skip to content

Dandelion Breeze – Now Available

So after a getting rejected and updating the app, Dandelion Breeze was accepted this morning and is now available in the App Store. Really excited to finally have it available to people.

One of the more interesting parts of developing watch apps was going through this initial submission process. I read plenty of docs, stayed on top of the forums, and did everything I could to make sure that I would make it through first try. Didn’t make help, still got rejected.

This sums up how I felt going into review, so when I was rejected it wasn’t a terrible surprise. The reason for my rejection was the following,

10.1 – Apps must comply with all terms and conditions explained in the Apple iOS Human Interface Guidelines

10.1 Details – Your Apple Watch app icon does not comply with the Apple Watch Human Interface Guidelines.

Specifically, since your app’s background color is black, your Apple Watch app icon does not appear circular.

Next Steps

Please modify the Apple Watch app icon with a lighter background color to ensure that it is recognizable and appears circular on the Apple Watch.

Now I’m not sure where in the linked HIG page it says anything about app icon background colors and making sure it appears circular, but I do understand the intent of this tester brining this issue up. Since the watch background is black, my icon would appear as an irregular shape, creating nonuniform spacing between the surrounding icons. This is bad for the user and makes the os feel less polished. So I understand why this was flagged, happily changed the icon and resubmitted.

What I would like to see from Apple, and I know I’m not the first to ask for this, but coming from console development I’d love to see cert requirement list. Yes, Apple does publish some guidelines, but they’re vague and incomplete. For instance, 2.1 (Apps that crash will be rejected) and 2.2 (Apps that exhibit bugs will be rejected). When was the last time an app you used crashed or had a bug? How does Apple test these? Are there steps that me as a developer can do to reproduce their test scenario? Console cert docs are typically an Excel sheet that that have detailed explanations as to what they’re testing against. Sure, it cost some money to go through the cert processes, but at least you know what you’re getting into.

I don’t assume Apple will change much in the way the do their testing or in the docs they make available to developers. That being said, I hope over time the process improves.

Be First to Comment

Leave a Reply

Your email address will not be published. Required fields are marked *