02-28-2013 11:13 PM
I got a super quick response on my BFB submission, which kind of makes me think that maybe they didn't test it completely. That said, it was rejected, and I'm not sure I agree with their reasoning. Would appreciate the insight of others more objective than I, so that I can determine how to proceed.
You can check out my app at the website http://www.authomator.com/ and on BlackBerry World at http://appworld.blackberry.com/webstore/content/22
I've pasted the relevant part of the rejection here:
Specifically we found your application does not meet the criteria as outlined in user benefits and would encourage you to consider enhancements like:
I'll start with the easier points. For service integration, I've built-in features like BBM Invite to Download, BlackBerry Advertising Service (banner ads at the bottom of the free version), and BlackBerry Payment Services (in-app upgrade to unlock active frame feature, and remove banner ads). Technically, Invocation is also incorporated, based on the links in the Help/About page. I don't see how I'm not integrating a BlackBerry service, but perhaps I'm wrong.
In terms of differentiating from other apps in this category, I can outline the following:
a) It actually works. You'd be surprised at how few of the other apps do.
b) Using the camera to scan QR codes. None of the other apps do this.
c) Displaying updated codes on the active frame. If you upgrade, you unlock this feature, which lets you display your 3 favourite accounts on the active frame. They update whenever the code changes, so you always have the most recent code to login with.
Finally, for the UI guideline portion, I can appreciate that there is a difference of opinion here. The app is written entirely in Cascades, with some minor customizations. You can see the custom progress indicator that we've built to countdown the expiry of the code. This is not a native Cascades control, but it's built using Cascades controls and we made the effort to make it look and feel like a Cascades control.
Moreover, we did take liberties with how items in the list are shown and highlighted. Each account does not share the same colour indicator, so when you highlight/select an item, it's not the native Cascades blue. I can agree that this may be different than what the UI guidelines might intend, but it doesn't preclude it.
The rest of the UI follows the guidelines in my opinion. The cross-cut menus, action items and system menu all follow the guidelines. We even followed the guidelines about deleting items.
Anyway, that's my opinion about the rejection. Would appreciate the community's feedback, and perhaps input from BlackBerry as well. I'd like to resolve these issues before I re-apply.
Thanks for reading.
02-28-2013 11:44 PM
02-28-2013 11:49 PM
Your main problem is assuming that there is a corolation between your app and the feedback you recieved.
03-01-2013 06:39 AM - edited 03-01-2013 07:09 AM
Careful now Ebscer that's dangerously close to being funny, sarcasm's not looked on too favourably in these here parts.
I laughed anyway!
I think the problem you might have is not knowing what they looked at as your app needs further purchase to unlock a good deal of the 'social' features. The ones you have initially are more for you than the user, in your description you quote,
'BBM permissions are only used to enable Invite to Download, so that you can tell your friends how to get their own copy of Authomator. BBM is not used for any other purpose'.
It's been speculated in these forums before that implementing services which just benefit you aren't really what the program is looking for. And from a marketing perspective by the way pointing out to users that your app is limited probably not the best thing to do.
Having looked at your competition do any of them use invocation if so then that's probably the explanation for the quote about a differentiator.
I didn't get very far with it sorry as I'd need to read up on these codes, as someone who hasn't used them before your app pretty quickly stumped me with no extra help available to guide me through but then perhaps you're happy with that and people who don't know anything about these aren't your target audience, perfectly valid.
I couldn't see any non-cascades elements after 10 minutes of playing with it and as far as I got.
So apart from that your best bet is to try and talk with someone from BlackBerry and/or wait for the appeals process as Peter pointed out.
03-01-2013 11:59 AM
03-01-2013 07:35 PM
Just to provide more evidence of the app's utility and suitability for Built for Blackberry, I'm providing links to two reviews done about it:
03-01-2013 08:46 PM
All good evidence for the appeals process.
Just as a thought on the social side, can you not have groups within a company needing a single service? In which case this would bring the sharing element back in.
Sorry wish I had the time to investigate this area more to maybe help you out more.
03-03-2013 12:48 PM
You use THREE BlackBerry services so that argument is nonsense. According to the guidelines you're supposed to use at least one.
The UI thing appears to be a 'blanket rejection thing'. It makes no sense to say that without extra explanation.
The 'more features' thing doesn't apply to this app at all. It does exactly what it needs to do. Adding irrelevant features would actually lessen the app's value.
I see two possible outcomes:
1: You use the appeal process and get accepted (To me this app looks like one that should). Maybe some UI tweaks can be done but that shouldn't keep it from getting accepted I think.
2: They will clear up the 'too simple / single purpose' reasoning and it will turn out that anything that doesn't have / require many screens and other inherent complexity is simply not eligible for this program.
My 2 cents.
P.S. Peter, sorry for the annoying, hard to read rants.
03-03-2013 04:23 PM
P.S. Peter, sorry for the annoying, hard to read rants.
I don't think anything in that post was a rant. It's constructive, and allows for the possibility that this particular incident is a mistake and could have a different outcome once the ongoing process changes complete... I liked that post.
The rants are the ones with the endless "OMFG BB is so pathetic can't they do anything right" stuff in them.