09-04-2012 03:28 PM - edited 09-04-2012 03:34 PM
Reading this page >> https://developer.blackberry.com/builtforblackberr
1) Andriod/AIR Development is noticably missing - I know we want to encourage native experince but RIM allows Andriod and AIR apps so why do they not qualify? We know even RIM writes their original PlayBook browser in AIR so AIR is definitely a quality form of development. Likewise for Andriod, why should we exclude our Andriod friends if they can make a good app which can run which dont use RIM's framework. As long as its not ugly why not? (think Tiny Bird which runs fine on PlayBook and is almost not noticeable as an Andriod app to the regular consumer).
2) The guidelines are too restrictive, a lot of great apps can be made without the use of any of the Service Intergration criterias (of which 1 is required to qualify). A great app that we know is coming to BlackBerry 10 is Blaq, as far as I know (from the PlayBook version) none of these services are being used. Blaq is one of the most purchased applications by an independent developer in BlackBerry App World for the PlayBook. If Blaq doesnt qualify one must wonder if these rules are too tight for the regular Joe developer who can still make great apps but might not need to use all these frameworks.
3) Developers need a privary policy? Those who can afford to make one wont qualify for this program to get the 10k (since they are big name devs which will likely make more than 10k), and those who cant afford to write one will need to write one to get the 10k. See the irony? Perhaps RIM can have a boiler plate template avaiable for developers who cant afford legal services to use....
4) Service Performance. - Apps will use CPU and memory, we get that and understand that RIM wants to minimize lag. That is fine. Lets put some numbers or benchmark examples in that so we know what to expect.
I know the intent is not to only to have the program for the 10 k offer but to have this as a benchmark of quality but let's reexamine how RIM defines quality and be less restrictive in the rules which developers are bound by. Lets encourage creativitiy and allow developers to use the tools and frameworks they want to make the great quality apps we all want in anticipation of the launch of BlackBerry 10.
Solved! Go to Solution.
09-04-2012 03:37 PM
The only part about this that I agree with is the exclusion of AIR apps. I agree, they should be allowed.
Otherwise, I think RIM's criteria are mostly fine as is.
09-04-2012 03:44 PM - edited 09-04-2012 03:49 PM
I have to agree with HorizonXP, here. The only reason Blaq isn't using any one of those services is because the majority don't exist on the PlayBook.
I know RIM is trying to push both WebWorks and Native as the top-tier platforms going forward. However, AIR should probably be included since they worked to get AIR/Flash developers onboard since the beginning. Those devs would probably feel abandoned, at this point.
Everything else is akin to what RIM pushed under the "Super App" paradigm so A+ for that.
09-04-2012 03:51 PM
09-04-2012 03:58 PM
I understand we want top quality A+ apps that great. The Built for BlackBerry Program encourages that yes but does this encourage other not as experinces developers who can make great apps? Check out the multitude of start ups who are doing application development, how many will follow these strict guidelines just to develop for BlackBerry 10 (as opposed to the other platforms)? We have to keep in mind while I am assuming BlackBerry 10 is amazing, we still have a lot of doubters out there and everyone is still doing this at a risk of developing for a fairly new, and some could say 'unproven' platform. If we want to continue on the momentum required to move forward with what is being built bringing in new quality developers to make BlackBerry 10 apps perhaps we want to lower or broaden the scope of the standards for the 10k guarantee. The 10k guarantee, I was told is to mitigate the risk for developing for the platform so we need to do just that for the developers. The Built for BlackBerry program can still be used with similar guidelines, but perhaps lower these guidelines for the purpose of the 10k program will encourage developers. Imagine a developer who makes a nice (but not A+) app who hits $1k and get 10k from RIM - do you not think they will be encourage to continue working on new (and better) apps? Keep in mind, the real value is not in the first BlackBerry 10 apps, its in what developers will continue to bring on board after these one time offers are over!!
09-04-2012 04:03 PM - edited 09-04-2012 04:05 PM
The thing about this program is it's supposed to encourage high quality apps. You should not receive $10K for porting your Android app or for writing a subpar application.
If your application is worth it, adding one of those services should enhance the experience for your end users as well as get you into the Built for BlackBerry program and guarantee you $10K if you make $1K in App World.
The goal (IMO) is for you to make the app so worthwhile that you are guaranteed to earn that money, regardless of whether RIM gives it to you, or your users do.
Keep that in mind.
09-04-2012 04:05 PM
09-04-2012 04:27 PM
I agree with HorizonXP and JCarty. If they did lower the requirement then people would make apps that would just meet the requirements instead of an A+ app. It would also drown out the quality app with the subpar because there would be a lot of them. We don't want app world to become like google play, where most app are useless or subpar
09-04-2012 04:33 PM
Perhaps here I am the minority and we are all worried about 'bad apps' which will infitrate the system, however, I would like to say that its probably unlikely a 'sub-par' app will make 100 paid downloads and $1,000s in revenue if things are in check (and if it does that developer may have the resources to improve their app). Once again, I'm not saying we need to lower the standards dramatically but boraden it to allow more choice in creativity in how developers make great apps and encourage the continual build up of great apps in App World .
09-04-2012 04:36 PM