Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

Reply
Developer
Posts: 325
Registered: ‎10-01-2012
My Device: Dev Alpha C, Playbook 32 GB
My Carrier: BleskMobil

Dev Alpha C rules - time to reconsider them?

[ Edited ]

Hi,

 

I'm browsing BB World and I found surprisingly high amount o mass **bleep** producers, thant clearly point to Dev Alpha C program.

 

Look at 

https://appworld.blackberry.com/webstore/vendor/11938/ (and the same person again at https://appworld.blackberry.com/webstore/vendor/32905 and at https://appworld.blackberry.com/webstore/vendor/58407)

 

Look at https://appworld.blackberry.com/webstore/vendor/10180 or at https://appworld.blackberry.com/webstore/vendor/57816/

 

These people definitely don't produce high quality apps but clearly point to get as much Dev Alpha C points as possible. They also block review process.

 

I spent three months learning BB10 platform. I produced about four or five apps with intention to give some utility to users as I wanted to help BB to get good quality apps. 

 

But in "competition" with people mentioned above (and I'm sure it is just tip of the iceberg) I have no chance to get Dev Alpha C.

 

My most popular app has 71 reviews and 4.5* rating but it does not matter. 200 points for **bleep** are equal to 200 points for popular app. 

--------------------------------------------------------------------------------------------
-- My Blackberry 10 app at http://blackberry.hubalek.net
-- My Android apps at http://android.hubalek.net
Developer
Posts: 368
Registered: ‎06-30-2012
My Device: Playbook, Z10LE, DevAlpha C
My Carrier: Telenor, Mobitel

Re: Dev Alpha C rules - time to reconsider them?

[ Edited ]

And you are suggesting what? Every developer has it owns styrategy, how to develop apps and which kind of apps. RIM wanted large quantity of apps,  portathons was a tool for that, i guess they don't want again same situation like it was with Playbook. It's their legitimate marketing strategy.

 

If you spent many months developing few apps for BB10, than they are high quality apps, and should be B4BB. That will give you high point boost to get DevAlpha C, right?

Developer
Posts: 325
Registered: ‎10-01-2012
My Device: Dev Alpha C, Playbook 32 GB
My Carrier: BleskMobil

Re: Dev Alpha C rules - time to reconsider them?

So do you think that it is good for users if they have the same Rampunzell Fairy Tale in three the same apps from the same developer?

App discoverability on BB World is poor right now so I don't see benefit from such a spam.
--------------------------------------------------------------------------------------------
-- My Blackberry 10 app at http://blackberry.hubalek.net
-- My Android apps at http://android.hubalek.net
Developer
Posts: 368
Registered: ‎06-30-2012
My Device: Playbook, Z10LE, DevAlpha C
My Carrier: Telenor, Mobitel

Re: Dev Alpha C rules - time to reconsider them?

[ Edited ]

I don't think it's good for users, but RIM was stimulating that, i guess high numbers of apps in BBWorld are theirs adut in selling BB10 phones. If you are from EU, and I think you are,and  attended Amsterdam Jam, just add release of one of yours app for Q10, and you will get DevAlpha C for sure. In DevAlphaC T&C they say, it is one device per developer, so in that case, your eventual points for Dev C is not an issue.

 

AppStore and Google Play stores are bragging with high number of apps, so RIM wants to do the same.

Developer
Posts: 325
Registered: ‎10-01-2012
My Device: Dev Alpha C, Playbook 32 GB
My Carrier: BleskMobil

Re: Dev Alpha C rules - time to reconsider them?

I have already updated one app for Q10 but I didn't attend BB Jam so ... cheese

AppStore and GPlay are bragging with high numbers but app discoverability there is significantly better so nobody cares about bottom 90%.

Also GPlay does not review apps so your app is on air within hours so I don't care that other thousand people is releasing in the same day.
--------------------------------------------------------------------------------------------
-- My Blackberry 10 app at http://blackberry.hubalek.net
-- My Android apps at http://android.hubalek.net
Developer
Posts: 368
Registered: ‎06-30-2012
My Device: Playbook, Z10LE, DevAlpha C
My Carrier: Telenor, Mobitel

Re: Dev Alpha C rules - time to reconsider them?

I'm too annoyed with this ridicoulos wait time for approvals, but that's not developers fault, RIM did not prepare itself well for this number of apps, it's their fault.

Developer
Posts: 671
Registered: ‎03-21-2012
My Device: BlackBerry PlayBook 16GB
My Carrier: Vip

Re: Dev Alpha C rules - time to reconsider them?

Boooo, easy ~$20k + bunch of Dev Alphas B/C :smileysad:
Developer
Posts: 173
Registered: ‎12-10-2012
My Device: Dev Alpha C
My Carrier: -

Re: Dev Alpha C rules - time to reconsider them?

Although multiple rupunzels aren't exactly appealing to users, or probably what Blackberry really wants from developers, keep in mind that quantity over quality is what Blackberry wanted from the portathons. They may not admit it, but that's simply how the portathons were set up. And from a marketing perspective, there is nothing wrong with that -- they had a certain number of apps needed for the BB10 release, and it was a unique way of getting there.

 

Now, as to the Alpha C, they could be a bit more strict, perhaps taking into account quality of certain developer apps, or weigh things based on the fact as to if they think the developer will port their apps to the device. But that may be a bit too much work for them, seeing as they have had a backlog of apps to review as it is.

 

And even in a mass of mediocre apps, there may be some gems, even if simple gems. I expect there are some developers out there who will look at the original poster's apps and say they are too simple also, so don't deserve an alpha C -- it's all relative. Maybe it would be best if Blackberry also took into account how likely they thing said developer will use the Alpha C for porting, vs someone who just wants to collect devices (not sure if there is even benefit to that, if they end up bricking them)... but that adds a layer of complexity to the rule process that may just create more problems.