Opinion
Ridiculous App Store Rejections
Monday, November 9th, 2009 | Opinion | Comments Off
Two more ridiculous App Store rejections hit the web the past week.
The first is MacWorld’s iPhone Superguide. It was rejected because it contained the word iPhone and a picture of an iPhone. Come on Apple! ITS RUNNING ON AN IPHONE! Why they can’t use the name or picture boggles me.
The second was rejected because cartoon versions of politicians were included in the app. OH NO! People might recognize their representative! And find information on them! We can’t have that now… My favorite line for the article is:
Hard to believe that anybody could be this stupid and blind. Maybe they just have a monkey doing the approval of their apps, and he throws a dart at a dartboard with “approved” and “rejected” targets on it and whatever it hits is the fate the that app.
This just gets stupider by the day.
Unbelievable: Apple’s FCC Repsonse
Sunday, August 23rd, 2009 | Opinion | Comments Off
While I personally disagree with the FCC’s involvement with the recent iPhone/Google Voice controversy, Apple’s response completely boggles the mind.
First, Apple starts off with some complete BS about the store, the number of apps, and how it functions. While the app store is much better than any prior cell phone app development and distribution, it still sucks in comparison to the Mac- especially because it doesn’t have to (more on that later).
Next, they describe three core reasons why apps are reviewed: “protect consumer privacy, safeguard children from inappropriate content, and avoid applications that degrade the core experience of the iPhone.” None of these points to good reasons why apps HAVE to be reviewed. The first will be quickly found out by the community. I’m not a child (and many iPhone users aren’t either), so I don’t need to be dictated too, so reason number 2 is bunk. And finally, the third reason assumes I can’t choose which apps DON’T hurt how my iPhone works. Actually, having MLB At Bat or AOL Radio in the background DOESN’T hurt the core experience. In fact, preventing those apps from running in the background HURTS the core experience- because I have to stop them to check email, text, or do anything else. So get off your high horse Apple.
Then they outright lie about the approval process: “When there is an issue, we try to provide the developer with helpful feedback so they can modify the application in order for us to approve it.” HAHAHA. Most of the time they just say “The app doesn’t comply with out guidelines. Its denied. Suck it, dev.” Many developers only WISH they provided helpful feedback. And finally (just in that paragraph): “95% of applications are approved within 14 days of their submission.” THAT ABSOLUTELY SUCKS! That should be 95% is approved in within ONE DAY. 14 days in an insanely long time- especially for bug fixes.
Now we start in on the answers to the questions. Q1 answer: “Contrary to published reports, Apple has not rejected the Google Voice application, and continues to study it.” THAT MEANS ITS REJECTED. If its not approved, its rejected. Period. End of story. Stop lying. Besides, it DOESN’T alter the user experience- IT CAN’T YOU MADE SURE THAT NO APP CAN AFFECT ANYTHING. Do you not use your own product Apple? Does the Phone “app” get replaced? NO. It disables visual voicemail? HOW? Only if you CALL A COMPLETELY DIFFERENT NUMBER! Jesus, its like working with 80 year olds using an iPhone. Apple must thing we are 8 year olds with an IQ of 2. Let us decide Apple.
Okay, after a bunch of non-answers to questions, we learn that there are only 40 app review. WTF? For “65,000+ apps”? That’s insane! No wonder it takes 2 freaking weeks to approve an app. Double that app, or triple it.
Oh, and this is a complete lie: “In many cases we are able to provide specific guidance about how the developer can fix the application. We also let them know they can contact the app review team or technical support, or they can write to us for further guidance.” RARELY do they provide specific guidance, usually its “Your app sucks. Try again,” to paraphrase the email received. And NEVER can the contact the app review team or write to them for further guidance. How many blog posts do developers describe it as a black hole to find out what is going on with there app. Apple is out and out LYING to the FCC.
But what is most frustrating is that none of this is necessary. There doesn’t have to be the App Store (AN App Store is okay, but not THE App Store). There doesn’t have to be a review process. There doesn’t have to be a review team. There doesn’t have to be so much bad PR for Apple.
So many problems can be solved in one fell swoop- Allow any app on the iPhone. It will not hurt anybody. It will not hurt the “children.” It will not hurt the network. It will not hurt the iPhone. But it will make the iPhone the platform nobody hates, and nobody wants to leave.
Stop being dumb and stupid, Apple. Open up the iPhone, and watch your dominance grow.
AP- Completely Misguided
Friday, July 24th, 2009 | Opinion | Comments Off
The news organizations continue to miss the point. The AP thinks that they will get revenue even by people linking to their stories. However, they completely miss the point of the web- to communicate between people. Charging for even link will only mean that less people will link to the story(whether because they refuse to give into such extortion, or because they simply can’t afford it), and hence that the AP will become increasingly irrelevant. They are shooting themselves in the foot.
A Better App Store
Saturday, July 18th, 2009 | Opinion | Comments Off
The iPhone App Store insanity continues to amaze me. First, there are the inane rejections over stupid little things- like the fact that is possible to download the Kama Sutra in a book reader app. Then Apple fixes that by requiring 17+ rating for any app that can access the internet. Yet Safari has no such warning.
This “let’s protect the children” junk annoys me to know end. It doesn’t actually protect the children- because they will always find a way around it anyway. But it does frustrate normal users and developers. Apple needs to stop being so overbearing in the App Store approval process, as well as the functioning of the iPhone rating system itself.
But this gets back to a bigger problem- reviewing and approving apps in the first place. Craig Hockenberry points out many of the problems with the App Store. Now, there is no doubt the iPhone environment is great, as he shows as well, but I believe the problems outweigh the good. Problems such as too slow approvals affecting bug fixes, no paid upgrades, unclear rules for submissions, and product evaluations inaccurate.
Craig also offers solutions to such problems, including a $999 premium service to help speed approvals along (which Manton Reese rightly derides). However, this is all completely ignoring the root of the problem- only allow Apple approved apps on the iPhone. All of these other solutions are like trying to put a new coat of paint on house whose foundation is sinking.
Apple needs to rethink the entire iPhone application ecosystem. By requiring approvals for all apps on the iPhone, Apple is waiting time and money on those approvals. They need to hire hundreds of approval employees. They waste the time and money of the developers as well, as instead of selling when they are ready, they have to wait an unknown time until its ready, and they don’t even know if it will be. This is not to mention all the problems with iTunes Connect and ensuring certificates are working correctly.
All of the complaints by developers would go away instantly if Apple stopped requiring approval before apps were allowed on the iPhone. Developers could just offer an .ipa package that iTunes could install. Apple of course could still only offer apps on their App Store that they approved of. They could also pull any apps that were malicious, such as viruses or trojans. It would also pretty much kill the jailbreak community, except for the purposes of unlocking.
This environment works great on the Mac, and there is no good reason it couldn’t work great on the iPhone. Hopefully Apple and Steve will wake up and realize this has all been a huge waste of time.
Until then, the iPhone App Store will be a source of complaints, and will not live up to its potential.
Another Example of Bad Customer Service
Friday, July 3rd, 2009 | Opinion | Comments Off
Volitans Software holds Customer Service in high regard. We take care of our customers whenever they have a complaint. If they need a discount or a refund, we process that quickly. I make sure of that because without customers there would be no Volitans Software. I’m also a customer as well, so I know the other side too.
So when I come across something like this it gets my blood boiling. The jist of it is that flypenfly was sold defective RAM from OWC that did not work properly in his MacBook Pro. It only worked in 9600 mode, but not 9400 mode. He contacted Customer Service, they identified the issue, and sent him new RAM.
But then they charged him $30 for the new RAM, because it was an “upgrade”- except it wasn’t, because the old RAM was defective. They will not budge, and that is outrageous. I was planning on upgrading my MacBook’s HD from OWC, but there is no way that is going to happen now. I will just buy it from NewEgg now.
Its sad, since OWC had some nice products. But Customer Service shows me what type of company a business is, and OWC doesn’t seem like a good one.
Rest assured that Volitans Software will always communicate you in a profession manner, will listen to all complaints, suggestions, and other comments, and will never charge anything the customer does not want.
Update: This is a little late, but if you followed the forum thread, OWC finally fixed the issue to their customer’s satisfaction. I’m happy to say that everything worked out like it should. They also emailed me and said “but issue just should never have happened. And as you can tell from actions both past and present, we take our reputation and our commitment to the customer pretty seriously from the very top.”
Given that they resolved everything perfectly, I actually ordered a new HD and a RAM upgrade for my MacBook last month. As usual, everything came quick and correct. I have always been happy with OWC, and I would highly recommend ordering from them.
Tweetie for Mac- Excitement followed by disappointment
Tuesday, April 21st, 2009 | Opinion | 1 Comment
Yesterday Tweetie for Mac was released. I have heard that Tweetie for the iPhone was awesome (haven’t tried it yet because there is no free version), I was excited about a new app from a developer who already had an awesome app. I downloaded it and was very disappointed at the interface.
For starters, there is no Growl support. I rely on this to see new tweets, so I don’t have to catch up later. I hear this is in the works, however it is still disappointed without it included in this version.
My biggest grip with the UI however, is the separate tweet window. This complete ruins the Twittering experience for me. Whereas Twitteriffic (and most other Twitter clients) have the field at the bottom, Tweetie opens up a new window for each tweet. I have to change focus from one area to a completely random area each time- instead of one single location. I emailed the developer Loren Brichter about my issues, and he replied the following email. He gave me permission to repost it, and while my response to him was not the following, it was very similar:
My sincerest apologies for your disappointment at that comment. There
were a *ton* of reasons why I went went the new-window compose route.
A few (if you’ll hear me out):- You can compose a few at a time if you want to take time to compose
your thoughts
Which is nice, but nothing I’ll ever use. I see a Twitter, and reply. I’ll have a thought, post it on Twitter, and be done. I don’t need to draft 140 characters.
- The vast majority of the time for the vast majority of users is
spent *reading* tweets, not writing them. an appropriate amount of
screen real estate was given to composing on the main window given
this common-use-breakdown.
There is not much real estate being taken up by a text field at the bottom of the main window. And while most people do read more than write, that still doesn’t mean its a good UI choice to remove the easy-to-use- bottom field.
- I wanted the app to *feel* less like a toy, and more like a
communications tool. I wanted it to *feel* more like Mail than iChat.
I wanted (though my choices in UI) to subtly encourage users to THINK
before they posted (and I believe people have a tendency to put more
thought into an email than they do IMs). The weight of an independent
compose window provides this importance. It’s the same reason why I
chose not to have ENTER post a tweet, Command-ENTER is the shortcut to
post, and I think that extra modifier does its small part to make
users think before they tweet.
This is where Loren and I have our biggest disagreement, and since its a philosophical difference about Twitter, its huge. I feel Twitter is MORE like an IM than mail. Its 140 characters, about the same as an IM anyway. I don’t see the need to FORCE users to think before they tweet, so posting with COMMAND-ENTER (instead of the logical and better ENTER) is very frustrating. I don’t think it would help anyway, and it takes away from standard Mac UI and posting conventions that ENTER sends something.
- It’s a fantastic *general* solution, for example it works great with
the global keyboard shortcut (in the prefs) where you can bring up a
compose window from anywhere in the system. It also works perfectly
for the url bookmarklet. No special casing needed.
This is in fact awesome, and I really would like this feature in more Twitter apps
- If you think about when you write a tweet, your fingers *have* to be
on the keyboard anyway, so it’s a negligible amount of work to hit
Command-N.
Not until I’m actually ready to write a tweet though. I’m already scrolling with the mouse, in the general area of the tweet window. For Twitteriffic, I either click in the field or click on the reply button next to a tweet, then start typing. For Tweetie, I have to hit a command for a new tweet, or click a tweet then hit the command, then find where the reply window went, and start typing. Its a small and subtle difference, but it changes the Twitter experience drastically.
I completely understand that it may not be for you, but it’s really
important to me that you understand that the decision wasn’t
arbitrary. If it makes you feel any better, I had weeks of sleepless
nights thinking about this. The only reason I thought *not* to do it
was because people were just used to some other way – and that wasn’t
a good enough reason to switch to an (in my mind) inferior UI.
I certainly understand his reasons. But my retort is that the separate window is NOT mutually exclusive to the in-app field. They BOTH can be used, and I think the app would be much better for it.
Its a shame this one issue has to ruin what otherwise is a great app. It has a lot of features I would use- like viewing direct replies, and global app tweeting ability. In fact, I would certainly pay for the ad-free version if he added the in-app field. Unfortunately, it looks like he will not change his mind.
Which leads me to think maybe I should develop my own Twitter app…
Kerio and iPhone OS 3.0: Follow Up
Friday, April 17th, 2009 | Opinion | Comments Off
The last time I talked about Kerio and iPhone OS 3.0, my mail on my iPhone wasn’t working. To recap, Apple blamed Kerio, and Kerio wasn’t very helpful.
Well, I updated to 3.0 Beta 3, and that fixed the problem I was having. Now I can successfully read emails again on my iPhone. I realized how much it sucked to not have it. I’m not sure why Apple blamed Kerio, and yet an Apple update fixed the problem. Regardless, I’m just glad its working now.
As a side note, Kerio is now on Twitter. Which is a good thing for customer service. Its a great way to get feedback from your customers and address issues head on- even if they never contact the company they are talking about it. Even Comcast has had a lot of success at this. Its a good trend to see companies make an effort to listen to their customers.
Mr. Jobs- TEAR DOWN THIS WALL (part 1)
Wednesday, October 1st, 2008 | Opinion | Comments Off
And so he listened. The NDA is dead- finally. It was holding back developers and users alike. Apple received bad press because of it. Innovation was stifled due to it. And I don’t believe for a second that the NDA could protect any kind of IP. But you have to give Apple credit- they listened. Many people were angry and ready to jump ship. I know I was. This stops that- for now.
But it does not prevent it from occurring in the future. Apple still has a ways to go with the iPhone platform. The next biggest thing to kill the closed App Store. It is fine to have an App Store, but not the App Store. I can understand that users what to be sure applications to crash or kill their phone; that they would like some vetting of the applications. An App Store is perfect for that.
Nonetheless, keeping out all applications is harmful to the platform. There are many applications that Apple would not approve that could be useful. And on top of that, the process for submitting applications is horrible. A developer can work for months- months better spent on other task- only to have the applications rejected for some vague reason. That also stifles innovation. Developers will not risk writing the great applications, the game changing ones, for that reason.
The next step is to change the application approval process. Developers should submit an idea proposal: “Our application will do <idea>. This is how it will work: <operation>.” Apple then gives preliminary approval to the idea. The developer writes the application and then submits that to Apple. Apple then can ONLY reject for bugs or features that obviously deviate from the submitted idea. That is how it should be handled.
Still, this is a good day. Apple listened (however long it may have taken them). That is a good thing. That shows they do care, and they do follow the news. It shows that developers and users can change problems with Apple- even if its only the big ones. They should be applauded for this. Granted it is not the first time we have seen them do it, but it shouldn’t be celebrated any less because of that.
Thank you Apple, and thank you Steve.