Skip to main content

Intro

Create Apps to track users' activity, coaches and branches.

With RookMotion, you can build Apps for individual users (athletes, employees, insureds) and keep track of their activities. Also, you can create a product for multilevel organizations with chains, branches, and rooms structure, with relations, tracking, and monitoring for their User's activity.

RookMotion Core is the main component of RookMotion and will help you to store and manage:

  • Users
    • Their personal and physical information.
    • Tracking devices.
    • Trainings, summaries, and statistics related.
  • Activity centers
    • Center's information
      • Address, multimedia, and administrators.
    • Center's Levels
      • Chains, branches, rooms.
    • Users
      • Enrolment, activities, assistance, and statistics.

Resources

RookMotion consists of the following:

  • An API with a set of endpoints to manage the business logic of centers, users, devices, and trainings.
  • An SDK to accelerate your implementation process on Mobile and wearables Apps to handle Bluetooth connections with standard heart rate devices, trainings storage, and connection to RookMotion APIs.
  • Extra resources like code snippets, recipes, and design references help you create your app, saving a lot of time for thinking and researching.
πŸ’‘*Standard Heart Rate Devices mean devices with Heart Rate Measurement capability and Bluetooth exposure of the measurements according to Heart Rate profile specification. These devices can be, SmartWatches, sensors, and fitness equipment whenever they expose the Heart Rate Measurement via Bluetooth. A list of some of the devices already tested can be found here.
πŸ’‘Current available SDKs are Java/Kotlin, Swift, and React Native. If your App uses another platform, don’t worry, you can use RookMotion APIs with your own framework; You will have to handle the hardware and storage functionalities

Resources Functionalities

API functionalities​

  • Users
    • Create/edit/list/delete users
    • User Status
    • User information
      • Add/Show
    • User Physiological variables
      • Add/Show
    • User External id
      • Add/Show/Update/Delete
    • Sensors
      • Add/Show/Update/Delete
    • Trainings
      • Add/Show/Delete
      • Training info includes
        • Start time
        • End time
        • Type
        • Device id
        • Records
          • Heart Rate
          • Calories
          • Heart Rate Effort
          • Steps
          • Cycling
        • Summaries
          • Heart Rate (min, avg, max)
          • Heart Rate Effort (min, avg, max)
          • Heart Rate Effort Zoned (On each zone of effort)
          • Calories (min, avg, max)
          • Calories Zoned (On each zone of effort)
        • Statistics
          • Get summaries over a period
    • Business Logic
      • Handle Levels: Chains/Branches/Training Rooms
        • Create/edit levels
        • Set level information
          • Name
          • Logo
          • Address
    • Storage
      • Training, users, and devices on Rook Cloud Database

API comprises the following functionalities

SDK functionalities​

  • Communication with Bluetooth LE Heart Rate sensors.
    • Bluetooth
      • Start/stop discovery for nearby sensors.
      • Connect / Disconnect to Sensor.
      • Listen/Callback for Sensor connection/disconnection.
      • Get heart rate measurement notifications.
      • Get steps notifications (only for Rook sensors).
      • Get Battery level
    • Local storage (on app)
      • User information
      • User sensors
      • Trainings
        • Records
        • Summaries
    • Training
      • Start/Pause/Resume/Stop/Finish
        • Sensor connection and Hear Rate measurements reception
        • Storage of records
        • Calculation of summaries
      • Set training type.
      • Set Sensor
    • RookMotion API communication
      • Add/edit/delete User
      • Add/edit User information.
      • Add User physiological variables.
      • Add/Show/Delete User Sensor.
      • Add/Show/Delete UserTraining.
      • Show UserTraining statistics.
      • Business Levels
        • Link/Unlink User/Sensor to level (Chains/Branches/Training Rooms).
        • Show level information.

Out of scope​

RookLeague is a final product built using RookMotion you can test the Apps and admins for coaches and use them as a reference. Below we specify which functionalities were created directly on RookLeague and are not part of RookMotion; They can be replicated by you but at your app level.

  • RookMotion Core does not include data streaming and challenges; these are optional modules.

  • RookMotion Core RookMotion Core has no auth functionalities for final users, meaning their login occurs at your app level. Users have to log in to your app, not to RookMotion.

  • RookLeague FrontEnd is a final product built with React and RookMotion where coaches can administer users, trainings, and rooms.

    • The React source code to create a similar FrontEnd is not provided but
      • UX/UI references and assets can be provided.
      • Our API covers most of the functionalities shown there except for Administrators management. You will have to implement the logic to handle the administrators, roles, and security of your FrontEnd.
    • If you develop a similar admin, dashboard, or frontend, you must host it on your own servers; as a reference, Amplify or Netlify are good options for fast deployment.
    • If you already have an admin, dashboard, or FrontEnd, you can add RookMotion sections into your existing FrontEnd implementing the corresponding calls to our endpoints.
    • RookMotion API provides stats and historical data of User's trainings; your FrontEnd developer will implement the plotting, display, or graphs.
  • RookMotion Core SDKs retrieve training and stats data; the plots and graphs for this data should be developed at your app level.

  • RookMotion Core SDKs sync service to check internet connection and try to push the User new trainings and info updates must be implemented at your app level; the methods to verify internet connection and push the info are included; only the service must be implemented.

  • RookMotion Core SDKs has no login and logout methods since final User authentication is handled at your app level. Users have to log in with you, not to RookMotion.