Pages Menu
Categories Menu

Posted by on Jun 3, 2014 in Development | 0 comments

Get some Appiness with new App Review Service

Get some Appiness with new App Review Service

I’d like to introduce you to my latest invention. I’m actually really happy…err…appy with the way it turned out.


As any app developer knows, developing the app is only half the battle. Actually, I’d say its less than half the battle. The trick today is marketing. The days of “Build it and they will come” are over…the app stores are simply too crowded.

One of the core determinants for your app success is related to downloads and reviews. First, people who are looking to download your app will first look at how many downloads you already received and the reviews you received before making that split second decision whether or not it’s worth their time. Second, we know your placement on the charts is directly influenced by your download velocity and/or reviews received.

And you can’t typically “buy” downloads and reviews. If you’re caught doing this using fake IP’s or “waterarmies” your risk your app being removed from the app store.

And that’s where appiness comes in. is a unique app review service that puts your app in front of real people who will download it, play with it and leave you a review in the app store. And because it’s real people, it is not only safe, it has the added benefit that “friends will tell friends” if they like your app.

Check it out at and see how it can help your next app.

Did you like this? Share it:
Read More

Posted by on Apr 29, 2014 in General | 0 comments

Alexa vs SimilarWeb

Alexa vs SimilarWeb

Wow, what happened to Alexa? I run a busy forum…around 30k visitors a day with about 10million page views per month. I’ve been tracking the reports on Alexa and a newer entrant (to me at least), SimilarWeb.

I can’t believe how outdated and inaccurate Alexa is. I used to believe Alexa reports because, well, there was nothing else short of seeing the actual analytics. ¬†And I knew Alexa was an approximation only, but I didn’t realize how wildly inaccurate they are. I discovered SimilarWeb and the difference is night and day. In fact, it is scary how accurate SimilarWeb is. If I didn’t know better I’d have thought they’re siphoning of my analytics. They are seriously that accurate.

SimilarWeb has nailed it in terms of my weekly visitors, my bounce rate, my countries of origin. I mean, nailed it. Alexa on the other hand have it so wrong, I started wondering if it was even my site. They don’t even have the visitor countries remotely correct, something I’d have thought is really easy to obtain.

I guess sadly that’s the end of that project…perhaps it was the Amazon acquisition, perhaps they just don’t have the technology (or user base)…but fair play to SimilarWeb, they nailed it.

Did you like this? Share it:
Read More

Posted by on Mar 20, 2014 in General | 0 comments

Apple doesn’t get social media

Apple doesn’t get social media

Apple has done a marvelous job in cultivating a certain image, and as a result has a prized demographic of customers. However, for a company that has position itself so well, it is remarkably lacking in understanding social media and transparency.

My App was approved yesterday and then went into the “Processing for App Store” status. Normally this is good news. This means you’re about 30 minutes to a few hours away from being in the app store. 36 hours I’m still stuck in that status…along with hundreds of others. The surprising part is the lack of communication from Apple.

I logged a support ticket and they responded they’re aware of the issue. If that’s the case, why didn’t they alert me of that proactively – what is this costing them to answer these tickets? I mean, how hard could it be to have done a proactive outreach with some transparency. I’m sure it would go something like this:

Select * from app_catalog where status=”Processing For App Store” and status_change_date – current date > 24hrs

For each entry, email:

“Dear <name>, it has come to our attention that your app is “stuck” (for lack of a better word) in the “Processing for App Store” status. This is not because of anything you’ve done, and unfortunately there is nothing you can do to push it along. This is entirely our fault, but rest assured we’re working around the clock to get your app into the store. Honestly, we haven’t come to the bottom of this yet, but as soon as we know the issue we will send you another email with the estimated time to fix it. Please know that we understand how anxious you are to have your app in the store, as are we. There are literally <count(sql query)> users in the same boat so we’re working hard. Stay tuned for more updates, and again, sorry!”

That’s it! Nothing formal. Just transparent – a mea culpa of sorts. I’d have respected that, and above all, I wouldn’t have wasted their time or my time with a support ticket. It couldn’t have taken them more than 2 hours to pull that off.

Instead, hundreds of us sit here not knowing what’s going on and costing Apple money by opening support tickets and then taking to social media ourselves. This is a great example of where a company could have got out in front of an issue. And earned respect.

I suspect that, sadly, this is a case of corporate bureaucracy. Apple has people far smarter than me so no doubt anyone could have done this in their sleep. What held them back was the red-tape. Or the potential ramifications of doing something. Or the “not my job” syndrome. Or the “this is going to interfere with my KPI’s” illness. And worse, the thought that “I have this email but now everybody is going to add there 0.2c of what it should or shouldn’t say, and then it has to go to legal and then…”

Bad one, Apple. Bad one.

Did you like this? Share it:
Read More

Posted by on Sep 9, 2013 in Development | 0 comments is born! is born!

I finally submitted my app to Apple for approval. Here’s hoping for a quick approval process. is a crowd decisioning app. Although I haven’t updated the website properly yet, you can see it here at

Some technical information for those who are interested:

1. The backend is utilizing the excellent Parse BaaS

2. The app is built using xcode/objective-C. I am utilizing the Storyboard features extensively. This app has a surprising number of master/detail views (ie. Embedded segues) so I was really forced to get the hang of it.

3. In the interests of efficiency, I denormalized the data structure somewhat. For example, I don’t tabulate the vote count, I instead keep a running total. Maybe not a very pure approach but it minimizes queries besides being faster.

4. The hardest part of the app was controlling the HUD spinning icon ;) This is a rather ugly part of iOS, requiring activities to be run on a background thread so the UI can be updated. I really would have preferred this happen automagically so that I can just call HUD.start and HUD.end without worrying about thread management.

5. No wait, I take number 4 back. The ugliest part of iOS is managing the keyboard and UI TextFields when the keyboard obscures the field. Can’t believe you have to manually take care of this. Ugh.

Stay tuned for app approval!


Did you like this? Share it:
Read More

Posted by on Sep 7, 2013 in Development | 0 comments

Using the BaaS

Using the BaaS

I recently discovered and must say I’m very impressed.

I am busy developing an iPhone app and was about to write all the server side code in PHP when I decided to look around at some of the BaaS players. I found about 5 that warranted a closer look to the level of actually signing up and trying it out.

I settled on Parse because of all the ones I tried, Parse was the only one that from sign-up to example code execution worked completely flawlessly. I’m sure the others may be good, but given the sign-up process at Parse, it seemed very well thought out. Plus, the documentation is really good.

By using the examples they provide, I was able to get my initial photo upload working in a hour or so. Over the next week I was able to complete most of my app functionality, and it was great knowing the backend was taken care off.

I did find a few idiosyncrasies, especially when doing multi table join queries in that it was difficult to compare keys using an objectID and a String. Fortunately the forum is very active and very helpful. Most of my issues were related to me being a newbie at using NoSql type queries (hard to get away from thinking in SQL) as well as being new at native iOS development.

I now have to integrate push into my app. Parse has Push libraries and should make this a lot easier. Unfortunately I still have to go through the cumbersome Apple deployment process to get this working (no fault of Parse!).

Check out …. definitely very worthwhile. I hope to finish my app and submit for app store approval in the next 2 weeks.


Did you like this? Share it:
Read More