Forgot your password?

New Analytics Service Requires Yet Another Redundant Form from Developers

Yet another annoying form BerryReview Analytics Service 

We just covered the “BlackBerry Development School of Hard Knocks” this morning and RIM was kind enough to provide us with yet another example of this. Their newly released beta of the BlackBerry Analytics Service SDK for Developers requires developers to submit yet another form to register. I tried logging into the BlackBerry Developer Zone first and it still made me fill out the form again.

RIM could pre-fill about 95% of this form without asking me for this information yet again. They already have my full name, company name, address, telephone number, and email address from my Developer Zone account. Is there a reason they need to ask for it again? The only unique information they ask for is for a BlackBerry Analytics Service Account Name and User Name. Instead of just asking for those two pieces of information we have them asking for 14. We also have to agree to yet another terms of service agreement which is FOURTEEN PAGES LONG when I copied it into Microsoft Word. Oh and you have to scroll through all 14 pages to accept the agreement which is then emailed to you in full when you complete the registration. Is RIM legal really this anal retentive?

Please RIM I am begging you. Why do you have to do this to us? Is RIM’s philosophy to force developers through a gauntlet of fine print every time we want to use a service?

PS: So I registered and then it sent me a really complex temporary password which it made me change when I logged in. It then proceeded to log me out and ask me for my information yet again. My bank does not even do that…

16 total comments on this postSubmit your comment!
  1. After reading your school of hardknocks post, this is a little depressing. Making things more difficult just doesn’t make sense.

  2. What’s the purpose of such long winded…..

  3. They do the same with the beta zone try downloading something from there first you have to agree to 2 to 3 different things to get into the program then before you download you have to agree to another 2 things. That’s like 5 agreements.

    • Holy crap – beta is *beyond* ridiculous, especially if you’re browsing from your phone. I counted once – in order to register and get a new beta product installed, there is something like 15 page views involved.

      In order to simply download an app that you’ve already registered for, it’s 7-9 page views.

      Let’s not get into the inability for the site to remember your password — it’s really fun typing a complex password with symbols, numbers, and mixed case on a BlackBerry when you can’t even see the letters you’re typing.

      Every.
      Single.
      Time.
      You.
      Visit.

      I’ve mostly stopped using beta products because of the above – it’s pretty clear they don’t actually *want* me participating.

  4. COME ON RIM!!!! We get it… You wanna be known as most secure…. but its getting overboard now

  5. I really hope this doesn’t ruin too many developers’ opinions and initiative to develop for BB. Its so frustrating to see this happening when RIM is on the verge of amazing things with the PlayBook release and eventual release of QNX smartphones.

    Don’t ruin your chance now RIM! This is a KEY time to attract developers and make it as easy for them to develop as possible! Fix it fast!

  6. This is where I wish we could log in with out MyWorld IDs and have everything pre populated…….

  7. OMG the world is coming to an end lol. Okay to be fair I am not a developer and I have to say taking your word about the process it does sound a little frustrating. But I just want to point out the tone often used with RIM related stories. It often makes it seem like the company has done the unthinkable and that’s just not the case. The company needs to reduce its excess need of paper work to make the process more smooth at least that’s one of the problems pointed out. I can’t help and wonder if Apple or Android got everything right when they started. Actually, I know they didn’t. Did you hear any of the stories? No, because since those are geared at consumers most tech blogs don’t see a reason to pick on them or find they may lose potential readers. As BlackBerry users I get a little tired of these “so call” fair blogs that attempt to be fair on most tech issues but do a poor job at it. All I am asking is think about the tone used when writing a RIM story or reading a RIM story. I know the company has its fault but sometimes reading these blogs one would think all these faults would have surely put the company out of business. But year after year it signs up more consumers and increases it profit. Once it doesn’t do a little thing everyone jumps on it and over stats this point. I guess its good for RIM to have all these tech blog that care so much about there success right? By the way I am not trying to diss BerryReview because they do a great job keeping readers like me in the loop. All I am saying is tech blogs also understand although we may not know everything we are certainly able to tell when someone is trying to get a respond and when someone has some valid concerns and presented in logical and unbiased way. This article much like the original has some valid points but does it have to be come across like the world is coming to an end? Thanks guys and keep up the good job.

    • Hi Celticboi,
      You have a good point. The tone of the article is based in frustration. I would not mind if RIM asked me to fill out a form once, twice, three times, etc. Now just imagine if Google required you to fill out a new form for every one of their services that you wanted to use. Say you sign up for Gmail and want to use Google Reader. Then you move to Picasa, Google Analytics, etc. Now do you get what I mean?
      Each one of these things by themselves are not a huge deal but it feels like RIM does not take a step back and realize that asking developers to get a notary public to verify your identity is ridiculous. It means they have done little to no market research to see how easily that will turn off potential developers.
      What I am trying to champion is that RIM tear down the useless and ridiculous walls and barriers they erect in front of BlackBerry Developers.

      • I totally get how the current process can be frustrating. Like I said I get there is a very valid concern and one that should be pointed out. I too did not like having to log in every time I wanted to access App World as a consumer. I hope RIM moves to improve these changes because they do have a great product that works extremely well and would not want developers to not make apps or services due to this process. But I still believe the tone not just this story but all RIM story are largely negative and mostly based on assumptions rather than actual evidence and facts. I don’t believe a person truly wanting to develop would be deter so easily due to the process and only those who are looking for a reason will jump off using the points listed in your article. By the way RIM did post a respond if you are interested on their developer blog……..I have a feeling you may not be happy with it but just try not to write the article right away haha. Good work guys.

        • Ah that is a good point. RIM has not been doing well but we are always the first to point out when they do something right. I wrote this article as a response to a friend at RIM asking what I meant about the “BlackBerry development school of hard knocks.” Now he understands :)

  8. Really, with autofill, who cares?
    Maybe 20 seconds longer?
    And yes, I’ve been auto logged out after a temporary password has been changed (BTW that was webtrends, not RIM). Quit your whining and get to work.

    • Scott AutoFill is simply a bandaid for shoddy programming on RIM’s side. Just take the need for ANT scripts to build a PlayBook WebWorks app. For example, it takes 3-4 different convoluted command line entries to build a playbook webworks app. Why? Because RIM thinks that is normal…

      I am not saying that it is such a big deal in each case taken alone but instead of 1,000 developers having to deal with these stupid issues and “quit whining” RIM could simply fix it.

      In a “quit whining” world nothing would ever get fixed and that is totally the wrong way to introduce developers to your platform. “Welcome to the revolutionary BlackBerry PlayBook development tools! They are so amazing! Just don’t whine about why they are not…”

      • I should have made my point more carefully:

        This is not the battle to pick. The battles for the developer to pick are much bigger stumbling blocks:
        1) Inability to programmatically auto fill an SMS message in OS5.
        2) bugs in GPS management and data reporting. (e.g. inability to recover from a bad ephemeris downloads: requires a battery pull; no altitudes below sea level)
        3) The numerous bugs in AppWorld that affect developers.

        YA Form is a pea on the road to development. For RIM as a company, I’d much rather they fix the show stopping potholes.

        • While I do agree with the App World bugs I disagree that this is not the battle to pick. Once you are talking about OS specific bugs those are almost impossible for rim to root out after release. Also developers that run into them are already commited to the BlackBerry platform. New developers see all this beurocratic red taape and wonder if starting is this bad imagine how clumsy development is. It can take a new dev 1-4 weeks just to get an app in App World. That’s nutz!

          • Agree with you Ronen. This IS a battle worth having. RIM is all over the map when it comes to consistency to the developer community. And it feels like there’s little to no communication internally. I just don’t get a company, ANY company, can present such a disjointed impression to the world and expect to survive?

BlackBerry© is a registered Trademark of BlackBerry Limited. BerryReview is in no way affiliated with BlackBerry Limited though sometimes their lawyers send us love letters...

Copyright © 2007-‘2016’ BerryReview LLC