Summary
How to deploy an Android application on Pepper QiSDK tablet
You have completed an important lesson. You now know how to use Command Center, the SoftBank Robotics deployment platform. This will help you deploy your apps and control a fleet of robots for yourself or your customers.
Use Case Recap
What you have learnt: * What is Application Lifecycle on Command Center * How to set up of a tablet-only compliant APK * How to sign the application * How to upload an application on Command Center * How to deploy an application on a Pepper QiSDK robot
Glossary
The glossary introduces Command Center terminology used in this lesson. Each entry is composed of "Term: Description (Category)"
Robot: A robot defines either Pepper or NAO. (Robot)
Group of robot: A group of robots defines a set of robots. A robot cannot belong to several groups at the same time. A group can only be composed of one type of robot (Pepper or NAO). (Robot)
Serial Number: The serial number is the unique ID (UUID) of the robot. It defines the robot in all SBR systems. (Robot)
Mission: A mission is an application or a group of applications. This is the content you can deploy on robots. (Mission)
Dependency: Dependencies are missions / applications that you can associate to a mission. Thus, when the mission is deployed on robots, the dependencies are deployed at the same time. (Mission)
Cms mission: A cms mission is based on an application which allow the end-user to customize the content at any time. (Mission)
Non-cms mission: A non-cms mission is based on an application which cannot be customized by the end-user. (Mission)
Task: A task is the instance of a cms mission that was created by an end-user. (Mission)
NAOqi mission: A NAOqi mission is based on a pkg. (Mission)
Android mission: An Android mission is based on an apk. (Mission)
Commercial mission: A commercial mission defines a mission without considering the versions of the mission. (Mission)
Paying mission: A paying mission is a mission that cannot be downloaded for free. A licence is required to be able to get it. (Mission)
Technical mission: A technical mission will be visible on the Store only by SBR users and developers. (Mission)
Tag: A tag can be associated to a mission in order to filter missions on the Store. (Mission)
Contributor: A contributor is a user added as Major or Minor on a mission. He will have special rights on the mission. (Mission)
Major contributor: A major contributor has the exact same rights as the owner. (Mission) \ He can :
- Upload new versions
- Edit the mission's details
- Submit the mission to QA
- Release the mission on the Store
- Distribute and revoke licences to other CC companies
Major contributor: A Minor contributor has limited rights. (Mission) \ He can:
- Upload new versions
- Edit the mission's details
Licence distribution: Licences can be distributed and revoked by developers to end-users so that they can deploy missions on their own robots. (Mission)
Public release: Releasing publicly a mission will display the mission on the Store. If the mission is a paying mission, users will not be able to download it without a license. If it is a non-paying mission, all users will be able to download it freely. (Mission)
Reference and Documentation
Command Center Glossary Download the Command Center glossary (pdf)
Command Center Developer Interface Deploy an app with Command Center Developer Interface
Contact Support team Contacting Support team to get your account to access Command Center
Command Center Client Interface View your robots and missions with Command Center Client Interface
Command Center Store Interface View all apps available with Command Center Store Interface
Contact
If you do not have access to Command Center yet: * Contact the SoftBank Robotics Support team
Any reactions and feedback about the website and the documentation provided? * Contact: devc-contact@softbankrobotics.com