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.

inside custom component

BlackBerry® World™ Development


Thank you for visiting the BlackBerry Support Community Forums.

BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)

BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.

"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."

- Kevin Michaluk, Founder, CrackBerry.com

Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.


Reply
New Contributor
Posts: 4
Registered: ‎03-28-2011
My Device: Developer
My Carrier: -

Understanding the shopping flow

Hi all,

 

Please point me to some docs/forum posts if all/some of my questions are explained elsewhere, I haven't managed to find an answer so far. I am a complete newbie in terms of BlackBerry App development, and we are now trying to port our Adobe AIR application to BlackBerry. I've read about different licensing models models and I have a problem understanding the overall flow in terms of keys:

 1. User buys an application

 2. A key is assigned (statically or dynamically) to this copy of application

 3. Application gets downloaded and installed

 4. What next? Does user need to check his email, get the key, and enter to the application? Or application knows the key already (how then?) How does the application verify that user has the correct key?

 

I've tried asking in Tables OS forum, but was sent here for more information.

Highlighted
Developer
Posts: 204
Registered: ‎07-09-2009
My Device: Not Specified

Re: Understanding the shopping flow

[ Edited ]

Best to retrieve the key yourself:  http://supportforums.blackberry.com/t5/BlackBerry-App-World-Development/Interface-with-the-BlackBerr...

 

You're probably just wasting your time, just forget about using keys until you have a major bestseller that's $5 or more, and even then it might still be more waste of time than increased sales.

 

You will get a lot of key-related support requests no matter what you do, and that time adds up.

 

 

 

Developer
Posts: 6,473
Registered: ‎12-08-2010
My Device: PlayBook, Z10
My Carrier: none

Re: Understanding the shopping flow

@mlamagra, it wasn't totally obvious, but the "Table OS" link and the "Adobe AIR" hint reveal that he's working on the PlayBook.

 

The link you gave is for the BBOS Java API and, unfortunately, no such API has been published yet for the PlayBook.  We're about to launch, yet have no idea how we'll be able to take advantage of the dynamic license model...


Peter Hansen -- (BB10 and dev-related blog posts at http://peterhansen.ca.)
Author of White Noise and Battery Guru for BB10 and for PlayBook | Get more from your battery!
Developer
Posts: 204
Registered: ‎07-09-2009
My Device: Not Specified

Re: Understanding the shopping flow

OK, I'm an April Fool a few days ahead-of-time.  Just warming up for Friday.

 

New Contributor
Posts: 4
Registered: ‎03-28-2011
My Device: Developer
My Carrier: -

Re: Understanding the shopping flow

Thanks a lot for the replies - so no reasonable API has been launched so far, and I think we're better stick with simpler models for now.