Licensing RhoElements
I get a lot of questions about how the licensing model for RhoElements works.
You can license your RhoElement runtime by visiting https://softwarelicensing.motorolasolutions.com/. The following documentation is taken from https://softwarelicensing.motorolasolutions.com/documentation/index.html, you should bookmark that site as it will always be kept up to date. Note that since the licensing site is shared between RhoElements and PocketBrowser much of the information below is worded quite generically.
Overview
The Motorola Solutions Software licensing site is used to manage your licenses for the following software products:
- Motorola RhoElements, http://www.motorolasolutions.com/rhoelements.
- Motorola PocketBrowser, http://www.motorola.com/pocketbrowser.
Note that it is not currently possible to license both RhoElements and PocketBrowser on the same device.
Accessing the Licensing Site
To license your software you will first need to log in to the Software licensing site, http://softwarelicensing.motorolasolutions.com. You will have received an email when your account was created detailing your log-in instructions, please check your spam folder as it may have incorrectly be categorised as such. If you have forgotten your password there is a link to reset it, provided you know your username which will be the email address given when your account was created. You must access the site using Internet Explorer or an extension / plug-in which mimics Internet Explorer if your browser supports that.
Once logged into the licensing site the header will appear similar to the below:
Example header shown on all pages of the Software licensing site
Information about your account is shown on the right side of the header, the username and company in this case are darryncampbell@motorolasolutions.com and PB Testing. The type of account is an End User account.
End users are presented with up to three 'tabs': "Orders", "Licenses" and potentially "Deployment Licenses" shown at the bottom of the header and explained further in the following sections.
You can search in the currently displayed 'tab' by entering your term in the search box, the filtered results will then be shown in the accordions.
Changing your Username and Password
Because the initially generated password is not very memorable the first thing you will want to do when logging into the site is to change your password. Clicking on the (edit) next to your username in the header will bring up the password change tab which defaults to an expanded 'Edit Username' accordion, use this field to change the username which you use to access the licensing site. Note that when changing your username you must choose a valid email address as this will also serve as the mailing address to which all licensing site emails will be sent.
Username / Password change screen with 'Edit Username' accordion expanded
To change your password click on the 'Change Password' heading to expand the accordion and from there specify your new password.
Types of Accounts
There are two main types of accounts on the licensing site, Resellers and End Users. Reseller accounts are designed for companies selling Software licenses and provide the ability to transfer licenses to other (End User) accounts but do not allow licenses to be assigned to devices. End User accounts are designed for individuals or companies to manage their licenses and provide the ability to assign runtime licenses to their devices as well as cancel licenses and set up deployment licenses.
If you believe your account is not of the correct type then please contact the Motorola Support Desk at http://www.symbol.com/services/contactsupport.
Licensing Restrictions
Different versions of software require different licenses and users are not automatically entitled to free upgrades. The table below shows which versions of PocketBrowser and RhoElements are compatible with which license types:
|
|
||||||||||||||||||
| RhoElements Licenses / Versions | PocketBrowser Licenses / Versions |
Tables showing which versions of software apply to which license types
Customers who have purchased a Software Support Contract ARE entitled to free software upgrades in line with the terms of the agreement. Please contact the Motorola Support Desk at http://www.symbol.com/services/contactsupport if you wish to apply for an upgrade.
Previous versions of all software are available from Support Central (http://support.symbol.com).
You can determine the version of software you are running as it is shown on the splash screen when the software starts up on the device. If the software is currently unlicensed it will also appear on the nag screen which is displayed every 5 minutes.
Deployment Licenses
Sometimes known as corporate licenses a deployment license provides the user with a way of licensing your software on multiple devices using a single key. Rather than licensing each device in your infrastructure individually by keying in the UUID you can apply to receive a single registration key which can be applied to multiple devices by simply scanning a barcode or adding a registry setting.
Deployment licenses are a legal agreement entered into between Motorola and the end user, as such they can only be applied for by the end user and not their reseller. For more details on applying for a deployment license see 'End Users: Applying for a Deployment License'.
End users will automatically be given the option to apply for a deployment license when they have purchased more than 50 licenses but users still must purchase individual licenses for each terminal being licensed. A deployment agreement does not permit users to license more terminals than they have purchased licenses for. If your company has multiple software licensing accounts whose total licenses add up to more than 50, but individually each account contains less than 50 licenses you may wish to merge the accounts, to do this contact the Motorola Support Desk at http://www.symbol.com/services/contactsupport .
End Users
End User Walkthrough 1: Licensing a Device
This is a simplified diagram showing the steps for an end user to assign a license to a single device. For a more detailed description including screen shots from the licensing site then please see the 'End Users: Licensing the Runtime' section.
Diagram showing stages for an End User to license a single device (click it to enlarge)
End User Walkthrough 2: Applying for a Deployment License
This is a simplified diagram showing the steps for an end user to apply for a deployment license. For a more detailed description including screen shots from the licensing site then please see the 'End Users: Applying for a Deployment License' section.
Diagram showing stages for an End user to apply for a Deployment License (click it to enlarge)
End Users: Overview of the Licensing System
When an End User logs into the licensing system they are given up to three 'tabs' and the Orders tab is shown by default.
End Users: Orders Tab
The Orders tab as seen by an End User (click it to enlarge)
The orders tab presented to the End User has up to two accordion panes, "Existing Orders" and "Deployment License Applications".
Existing Orders. For the majority of users the orders tab will only show the 'Existing Orders' accordion. Existing Orders displays the transactions sold to the end user by their reseller and the order number will therefore most often start with a 'T'. If you look at the above example you will see the top entry is T536428 which was transferred in the 'Resellers: Assigning Licenses to End Users' above. To see the licenses contained in each order then click 'View Order' in the same row as the order; this will also allow you to see how many of the licenses in the order have been allocated to devices.
Deployment License Applications. If you have over 50 licenses in your account you will also see the 'Deployment License Applications' accordion, which will be colored Red if you are entitled to a deployment license but have not yet applied for it. For more details on applying for a deployment license see the End Users: Applying for a Deployment License section below.
Note that the 'Deployment License Applications' accordion, if visible, will be the default accordion expanded when an end user logs in to the site and is also duplicated under the 'Licenses' Tab.
End Users: Licenses Tab
The Licenses tab as seen by an End User (click it to enlarge)
The Licenses tab presented to the End User has up to four accordion panes, "Assign a License", "Assigned Licenses", "License Cancellation Requests" and "Deployment License Applications"
Assign a License.
For most End Users this will be the most important feature of the licensing site.
This screen shows your pool of licenses available to license to devices. Each license type will show the number of free licenses available and to assign these to devices follow the instructions in the End Users: Licensing the Runtime section. If you have a deployment license for a particular license type you will be unable to assign additional licenses individually and therefore the 'Total Unallocated' column shows the number of devices you are legally entitled to register via the deployment license.
Assigned Licenses.
The expanded 'Assigned Licenses' Accordion (click it to enlarge)
The assigned licenses accordion shows the licenses you have assigned to individual devices, it will not show devices licensed assigned via deployment license. Each license shows the license ID as well as details you entered when assigning the license such as serial number and group information; the 'License ID' associated with each license is the easiest way of identifying licenses when contacting Motorola customer support.
Clicking 'View Licenses' to the right of any license will show the barcodes used to register the software on the device or allow you to download the registry settings, use this if you did not register the device when you initially assigned the license or wish to re-register the device after a complete wipe of permanent storage. You can also print or download the registry settings using the two icons on the far right of the table row.
Clicking 'Request Cancellation' will begin the license cancellation process, covered in more detail in the End Users: Cancelling Licenses section. Once you have cancelled a license you will no longer be able to view it but it will still be shown in the 'Assigned Licenses' table, as illustrated above. Even though it still shows in the table the cancelled license will have been returned to the user's pool of unused licenses.
Note that if you have a deployment agreement for a particular license type then assigned licenses of that type will not show in the 'Assigned Licenses' accordion even if they were previously licensed individually.
License Cancellation.
The license cancellation accordion pane shows the licenses which the End User has requested be cancelled. The process for cancelling licenses is explained in the End Users: Cancelling Licenses section.
The expanded 'Assigned Licenses' Accordion (click it to enlarge)
The table shows the progress of each cancellation request. When you initially make the request the status will be set to 'Awaiting Response' which means it is waiting for a representative from the Software Request Administrator team processes your request, you can view the status of your request by clicking on the 'View Request' link.
Deployment License Applications.
If you have over 50 licenses in your account you will also see the 'Deployment License Applications' accordion, which will be colored Red if you are entitled to a deployment license but have not yet applied for it. For more details on applying for a deployment license see the End Users: Applying for a Deployment License section.
Note that the 'Deployment License Applications' accordion, if visible, is also duplicated under the 'Orders' Tab.
End Users: Deployment Licenses Tab
The Deployment Licenses tab as seen by an End User (click it to enlarge)
Once you have followed the steps described at End Users: Applying for a Deployment License and successfully obtained your deployment license you will see the 'Deployment Licenses' tab in the header which can be used to manage your deployment licenses.
Clicking 'View License' will bring up the deployment license barcode which can be scanned, either on screen using an imager barcode reader or printed off to be scanned by a laser scanner. Registry settings can also be downloaded from this dialog to be included in your device build or deployment procedure.
The quantity column shows the number of licenses you have purchased for a particular license type, under the terms of the deployment license agreement you can not license more than this number of devices without purchasing additional licenses. Clicking 'View Agreement' will bring up a dialog similar to that shown below:
Example of a Deployment License Agreement screen (click it to enlarge)
The deployment license agreement is a legal agreement between the end user and Motorola Solutions stating how many devices can be licensed, which versions of software can be licensed and the order numbers thereof.
Note the deployment license agreement above does not correspond to the 'Deployment Licenses Tab' directly above it, the latter is the result of applying for the deployment license described at End Users: Applying for a Deployment License.
End Users: Licensing the Runtime
Most End Users will only use the licensing site to license their devices individually, to do this go to the 'Licenses' tab and click 'Assign License' against the type and version of software you wish to assign (See End Users: Licenses Tab).
Assigning a License to a Device (click it to enlarge)
You will see the dialog box shown above.
You can find UUID Part 1, UUID Part 2 and Checksum by starting the software runtime on your device; these values are shown on the licensing splash screen after you click the screen and press 'Next'.
PocketBrowser Licensing screen on device
RhoElements Licensing screen on device
A checksum is a way of ensuring you type in the correct values for UUID1 and UUID2, if you receive an error complaining the checksum is not correct then please ensure you have entered the two UUIDs correctly. Please do not use the UUIDs reported by the Windows Operating system, they may not be the same as those used by the licensing system.
It is not essential to give the serial number to license the device, however it is strongly advised to do so. The serial number can be used to identify the device when contacting support and will be used if the license needs to be cancelled at a later stage.
It is recommended you accept the default company display name, again this will aid in identifying the licenses if you need to contact support. The Group By field is a free text field into which you can enter your own grouping information, eg. you could group 5 licenses to "Arizona Store" and another 4 licenses to "Sales Team". These groupings will be shown in the 'Assigned Licenses' accordion as well as be search-able via the search box when the 'Licenses Tab' is selected.
After you have entered the required information press 'Submit' to be shown the 'View License' dialog:
The View License Dialog (click it to enlarge)
You can now license your device in one of four ways:
1. If your device has an imager scanner you can scan the barcodes directly off your monitor. On your device press 'Next' in the software licensing wizard until you are asked to 'Scan your company barcode', do so and then proceed to also scan the registration barcode. Your device should now report that it is licensed. Note in the above example image the company name is given as 'DEMO - NOT FOR RESALE', when viewing your licenses this will be replaced with your company name.
2. Similar to step 1 you can press the 'Print' button on the 'View License' dialog to print the barcodes and scan them with your laser or 2D scanner.
3. When prompted by your device to scan the registration barcodes you can enter the text manually, this is not recommended as the registration code is a hexadecimal key and it is very easy to make mistakes.
4. Pressing the 'Download' button will allow you to download some registry settings, apply these settings to your device to license your software. Note that this fourth method may, depending on your Operating System, be undone by cold booting your device unless you take precautions to ensure the registry setting persists across cold boots.
End Users: Cancelling Licenses
The most common reasons for cancelling a license are:
You have sent your device for repair and in doing so components have been replaced meaning the device's UUID has changed. The software no longer reports it is licensed on the device.
You made an error when licensing the device, for example you licensed the same device twice or you attempted to license the wrong version of your software.
License cancellations must be approved by a human and therefore will not be automatically and immediately processed online. Attempting to cancel licenses just to re-use the same license on a different device will not be approved.
To request a license be cancelled select the 'Licenses' tab and expand the 'Assigned Licenses' accordion.
Cancelling a License (click it to enlarge)
Locate the license you wish to cancel and select the 'Request Cancellation' link. You will be presented with the 'Cancel License Request' dialog shown above. From the drop down select the reason for cancellation and try to provide as much detail as possible, this will enable the request to be processed as quickly as possible.
The request administrator will either accept the cancellation request, in which case the license has been cancelled successfully or request more information from the end user; such as device serial numbers, duplicate license IDs or even just 'phone support'. You will receive an email when the status of the request is updated, if the status is 'License Cancelled' then no further action need be taken. Once cancelled although the license is still shown under the 'Assigned Licenses' accordion (with status 'License Cancelled') it has returned to your pool of unassigned licenses. If the status is 'Response Received' then more information is required of the End User, click on 'View Request' to supply additional information, this back and forth request / response will continue until the license has been cancelled.
Life cycle of a Cancellation Request, shown by clicking 'View Request' (click it to enlarge)
Provided the End User has given sufficient information about the cancellation request it is uncommon for cancellation to take more than a single request / response. The above screenshot shows the life cycle of an example cancellation request.
End Users: Applying for a Deployment License
When a user has 50 or more software licenses in their account they are entitled to apply for a deployment license (More). To apply for a deployment license expand the 'Deployment License Applications' accordion under either the 'Orders' or 'Licenses' tabs. If are entitled to a deployment license but have not yet applied for it then this accordion box will be colored red, if you are not entitled to a deployment license then the accordion will not be present.
Applying for a Deployment License Step 1 (click it to enlarge)
To begin the Deployment License application wizard click 'Apply online now' next to the type and version of software for which you wish to apply for a license.
Applying for a Deployment License Step 2 (click it to enlarge)
The deployment license is a legal agreement between the End user and Motorola Solutions and as such Motorola Solutionss require a physical address for the end user, if no such address is entered in the database then the wizard will complain at this stage. Please contact your reseller in the first instance or the Motorola Solutions Support Desk at http://www.symbol.com/services/contactsupport to provide your company address if it is not already in the system.
Enter the requested information and press 'Next'. The email address should be the the same as that shown in the licensing site header, in the top right hand corner of the screen.
Applying for a Deployment License Step 3 (click it to enlarge)
Read and accept the deployment license agreement, you can view this agreement later from the 'Deployment Licenses' tab.
Once you accept the agreement you will be shown the 'View License' dialog, again this can be displayed later from the 'Deployment Licenses' tab and is nearly identical to the 'View License' dialog described in the End Users: Licensing the Runtime section. A deployment license can be applied to a device in exactly the same way a traditional license can, i.e. scanning barcodes on the software runtime license screen or applying registry settings to the device but the deployment license will work on multiple devices, not just one device with a specific UUID.
Resellers
Reseller Walkthrough 1: Assigning Licenses to End Users
This is a simplified diagram showing the steps for a reseller to assign a license to an end user. For a more detailed description including screen shots from the licensing site then please see the 'Resellers: Assigning Licenses to End Users' section.
Diagram showing stages of Reseller assigning a license to an End User (click it to enlarge)
Resellers: Overview of the Licensing System
When a Reseller logs into the licensing system they are given three 'tabs' and the Orders tab is shown by default
Resellers: Orders Tab
The Orders tab as seen by a Reseller (click it to enlarge)
The orders tab presented to the Reseller has three accordion panes, "Create New Transaction", "Existing Orders" and "Transactions".
Existing Orders is expanded by default and contains the orders sold to the reseller by Motorola Solutions. Each order will contain a number of licenses and can be identified by their Order Number (assigned by Motorola Solutions) and their Purchase Order number, to search for a specific order type into the search bar in the page header. After typing a search term the shown orders will reduce to those filtered by the search term, the number of filtered orders is given in brackets in the accordion header. Note that entering a search term will filter all three accordions, not just the currently expanded one.
Transactions, when expanded, shows a history of past transactions, which are licenses sold by the reseller to an end user. Transaction Order Numbers will always start with a 'T'. To resend the transaction to your end user you can click the envelope icon associated with the transaction. Clicking 'View Transaction' will show which products were included in the order.
Create New Transaction, is used to send licenses to end users. Resellers can only send licenses they have in their pool which is populated by receiving 'Existing Orders'. The process of sending licenses to end users is explained in more detail in the section, 'Resellers: Assigning Licenses to End Users
Resellers: Licenses Tab
The Licenses tab as seen by a Reseller (click it to enlarge)
The licenses tab presented to the Reseller has two accordion panes, "Assigned Licenses" and "License Cancellation Requests". In most cases both of these panes will be empty, containing no licenses. The only reason licenses will be present under this tab is if the current Reseller account existed on the old licensing site, before 2008. In the past it was possible for resellers to assign licenses to devices however under the new licensing site they must transfer their licenses to an end user account (by creating a transaction), as explained in the highlighted yellow text in the screenshot. The sole purpose of this page is to provide a historical record of license assignments for this reseller.
Resellers: Customers Tab
The Customers tab as seen by a Reseller (click it to enlarge)
The customers tab shows all the users to whom you, the reseller, have transferred licenses. From this screen you can edit any of the attributes associated with the customer accounts such as contact name, contact address etc. A customer account can have multiple users, essentially multiple log-ins to the single customer account enabling multiple users within an organization to manage the end user's licenses. The customer account is initially created as described below in 'Resellers: Assigning Licenses to End Users' which creates a single user for the account whose email address is the same as the customer account's email. To create additional users for a customer's account click on 'Create User' in the same row as the customer and enter the user's email address; an email will then be sent to the specified email address informing them of their username and password. Emails relating to the customer account such as Order Confirmations will be sent to all users of the account rather than just the customer email address.
No facilities are given to delete users, merge customer accounts or modify user details. Please contact the Motorola Solutions Support Desk at http://www.symbol.com/services/contactsupport if you need additional assistance.
Resellers: Assigning Licenses to End Users
The most important function of the reseller account is the ability to transfer licenses to end users, this is achieved by selecting the Orders tab and expanding the 'Create New Transaction' Accordion. From here you need to enter the details of the customer who is to receive the order.
The Reseller's Create Transaction Screen (1) (click it to enlarge)
The first step is to enter the email address of the customer to receive the order, if this is an existing customer the Customer Email field will suggest existing accounts matching the input after a short delay, as shown above. Enter the email address and tab or click to move to the next field.
The Reseller's Create Transaction Screen (2) (click it to enlarge)
If the email address is recognized as an existing customer then the rest of the fields will be pre-populated by the existing data. You can take the opportunity here if needed to edit any of the existing data by clicking on 'Edit Customer Details' which will enable the text fields and click 'Finished Editing' when done.
If this is a new customer you will be required to fill in the customer details manually. It is recommended you fill in as much detail as possible, especially the address as this will be required later if the customer applies for a deployment license. At minimum you must complete the Customer Email, Customer Name and Country fields and you can complete the rest later via the 'Customers' tab.
"Purchase Order Number" can be used to assign your own order number to the transaction whilst the CC Email field can contain a comma separated list of additional email recipients of the order confirmation, separated by semi colons eg. a.n.other@motorolasolutions.com;recipient@motorolasolutions.com. Note that email confirmations are sent to all users under the customer account.
Once you have completed the details of the customer to receive the order you need to populate the order with licenses by clicking on the 'Add Order Items' button, shown below.
Adding Licenses to a Transaction (click it to enlarge)
The drop down list of products will only contain the types of licenses the reseller account has in its license pool, selecting a license type from the drop down will show the maximum number of licenses which can be assigned to this end user, this will be the number of licenses of this type in the pool. Enter the actual number of licenses to include in the transaction in the quantity box and click 'Add Item'. Repeat these steps to add more than one license type to the order. Press Confirm and an order confirmation email will be sent to the end user informing them they have received new licenses.
The above example has resulted in a single 'MPB 2.2 SW Maintenance Upgrade' license assigned to Order Number: T536428. We can add additional licenses to this order at a later date by expanding the 'Transactions' accordion, locating the transaction T536428 and pressing 'View Transaction'.
Adding Additional Licenses to a Transaction (click it to enlarge)
Items are added to the order in batches, when we first created the transaction the batch 1 licenses were attached. Using the above screen we can attach batch 2 licenses in exactly the same way. When you confirm the additional batch another email is sent to the end user informing them of their additional licenses.
Anonymous (not verified)
Dfghjkjjn
16 Replies
Awesome...very helpful.
Your reseller should be able to provide you with licenses. Darryn.
Ok, thanks!
From: Darryn Campbell
Sent: Wednesday, March 28, 2012 11:36 PM
To: Antti-Pekka Aaltonen
Subject: Re: <a href="Blog"></a> - Licensing RhoElements
Motorola Solutions Launchpad
Licensing RhoElements
new comment by Darryn Campbell - View all comments on this blog post
Hi! One question:
"To license your software you will first need to log in to the Software licensing site, <a href="http://softwarelicensing.motorolasolutions.com">http://softwarelicensin…; You will have received an email when your account was created detailing your log-in instructions,.."
How do I create an account which can be used to log in? There doesn's seem to be information about this anywhere.
How do you add a Deployment lic to the ET1 with out entering it manually? With WM it was a registry setting.
Hi Glenn,
To add a deployment license to an ET1 you need to create this file:
/mnt/sdcard/keys/rhoelementsFor first line of this file, enter the <strong>company name</strong> (the name which you would enter in step two of the manual licensing procedure)
For the second line of this file, enter the <strong>registration barcode value</strong> (the value which you would enter in step three of the manual licensing procedure)
Regards, Ben
I'm a bit confused about the licensing and terms.
I am writing (porting) a mobile app that allows consumers to scan barcodes and lookup the cash value on our website (we pay cash for used books, cds, dvds, etc.). We currently have over 200 customers using the Phonegap version of the app, but I'd like to convert the app to Rhoelements.
Does this mean I need to purchase a terminal or deployment license for EVERY customer? Or do I just purchase a single deployment license for Cyber Sprocket to build the app that we deploy on Google Play and Apple Store?
This make a big difference as a $60/download fee is WAY out of the price range for a free app we provide to our customers. Especially when Phonegap and Zxing are free GPL based implementations (and the basis of Rhoelements Barcode modules from what I understand).
$60/developer is one thing. $60/customer is not viable. This makes a BIG difference in the platform we choose to develop our apps and those for our clients.
Please enlighten & advise.
- L
~~~~ Help Cyber Sprocket Get Our R&D Grant ~~~~
We need 220 more votes by June 30th, 2012.
Visit <a href="http://www.missionsmallbusiness.com/">http://www.missionsmallbusiness.c…;, login, search for cyber sprocket, and vote.
It is free and takes less than a minute!
More info:
<a href="http://www.cybersprocket.com/2012/company-info/mission-small-business-g…;
~~~~ Thanks for your support! ~~~~
RhoElements barcode support is Motorola IP. In fact RhoElements is the only framework with realtime barcode scanning for both Motorola devices and general Android devices. As an enterprise focused product RhoElements is much cheaper than other enterprise platforms (WorkLight, SUP, Antenna, etc.). I think you will find that in the long run you are going to save a lot of money by using the current RhoElements features (advanced encryption, signature capture, shared container) versus using a consumer framework and trying to add them yourself. More specifically I think you will find that RhoElements barcode support outperforms (in speed and reliability) any of those open source implementations.
All that said, if paying for a framework is a true nonstarted you should be able to use ZBar or ZXing yourself and add to Rhodes as a native extension. You are correct that earlier versions of Rhodes did just this. This would give you free barcode support using the free Rhodes open source product.
Ok, but that didn't directly address the question. If we use Rhoelments and publish this app on Google Play and The App Store, do we need a $60 license for EVERY customer? More importantly, how is that licensed? Consumers want to download & use the app. Entering license keys or registering on a site is a no-go. The license would need to be "baked in" and pre-activated so they just download, scan, and go.
I understand the model may be more enterprise-oriented, but not having ANY barcode scanner support for consumer apps makes this problematic. 90% of our clients are direct-to-consumer. The first client has over 27,000 customers of which 80% have expressed an interest in getting our client's second gen mobile app to scan items. There is no way we can get their clients to pay $50 or even $10 for the app to cover a license and the client sure isn't going to spend $250k on a technology to cover this for the customer when they had it in the beta release for free.
As an aside, all device interfaces are using the camera for consumer Android or iPhone devices. Real-time scanning with laser or RFID is not available on those hardware platforms. The optical recognition process is going to be the same and most devices don't open up access to the CCD directly even through the NDK or OC libs and thus you need to go through the camera interface libs. How is a Motorola-specific implementation different than ZXing with real-time auto-focus, white balance, and pattern recognition? Is it faster? More accurate? Trying to get a true assessment for the few enterprise clients that may be interested in these things.
- L
Ah, OK. An app store app. As you increase the number of users the price per user on an goes down drastically. Work with your rep to get a quote.
That's good to know.
But can the apps be 'Pre-baked" with the license enabled directly from the app store?
You can add the license to your build.yml file, the instructions are at <a href="http://docs.rhomobile.com/rhoelements/rhoelements2-native#pre-licensing…;
Darryn.
I have a similar question about the licensing. I want to develop a barcoding app to run on motorola kit where we would buy some devices, then hire more for a week at a time as and when they're needed.
How will we license the hire ones? The device IDs will obviously be different every time we get them.
Why are you hiring devices? Are you developing applications on devices and then selling the kit on?
We're developing a barcode entry system that we lend to customers for events that they sell the tickets through us. Most of the year, 10 to 20 devices will be fine for us, so we'll buy them. Occasionally, say twice a year, we'll need another 20-30 scanners. We'd rather hire them than buy kit that stands idle for most of the year.
Ah I see, thanks. currently the only licensing option we offer is device level, i.e. you have to license the entire device. With the next release of RhoElements we are looking to roll out "Application Level" licensing, where you license a specific application on a number of devices.