We envision the following three primary use cases for businesses seeking to integrate with Riiiver, each with their own merits
For IoT device manufacturers
- Use the provided SDK to make smartphone apps compatible and interactive with Riiiver apps. As you discover new ways for your users to use the app, it becomes easier for you to increase the efficiency and development of your services.
- Try it for free. There is no cost required to download and try the SDK. We only discuss charges once you begin connecting devices to the production environment or when using the sponsor program.
- The web-based development tools provided on this site are also free, which you can use to develop the building blocks we call “Pieces.” Note that we review all Pieces submitted to us to maintain the integrity and security of the Riiiver ecosystem, so you can trust that the Riiiver Developer environment is a safe and worthwhile place to devote your efforts.
For consumer-service providers and consumer-product manufacturers
- Implement Riiiver connectivity that makes your service more convenient for your users and encourages long-term engagement. If a user can immediately access your service or information feed via a single push of their Riiiver-enabled smartwatch, it becomes that much easier for them to stick with you.
- Receive activity data demonstrating how users interact with your Riiiver integration to help drive effective improvement and development.
- You’ll be able to feature your iiidea (Riiiver functions) on the iiidea storefront. We’re preparing a fee-based sponsor program where you can both promote your iiidea, and receive GDRP-compliant data regarding how your users use them.
For internal company use
- Reduce development time and costs by adopting the Riiiver environment. Rather than starting from scratch and dealing with the inevitable bumps and delays that accompany the creation of a new platform, hit the ground running and expand on what we’ve already made.
- Propose that we develop or customize Riiiver features specifically for you. We’ll consider any request and, if achievable, provide estimates based on the expected scale and work hours.
The Riiiver infrastructure
What does it mean to connect your products and services to Riiiver? Let’s use our implementation of Riiiver as a case example. CITIZEN is a watch manufacturer. When we’re making a new watch, we usually blueprint a specific feature we want to include as follows.
In this example, the device maker (here CITIZEN) determines how the watch will function. However, if we want the watch to be compatible with Riiiver, we need to change our thinking to the following.
Essentially, the use of the buttons — our key input interface — is unlocked and made open for free use. Ordinary users, not just developers, can change the functionality of the watch’s input and output interfaces. The person who owns and uses the device can change the behavior of the buttons, hands, and sounds, and is allowed to mold the experience that they want to have with our watch.
For example, in the case of a fitness tracker app, the following native elements become available.
Provide these functions to users and encourage them to think about ways they could be used. Combined functions aren’t limited to specific devices; you can also connect them to other Riiiver-enabled services and devices. For instance, consider you have the following weather services.
By directly connecting these services to their device’s functionality, users can create “iiidea” on Riiiver. Below is an iiidea with the following function: press the 2 o’clock button to retrieve tomorrow’s weather data and indicate the forecast via the watch hands.
The user has connected their watch (device) to tomorrow’s forecast (service). Further, by making this idea open to the public, other users can disassemble it and use the individual functions to create new, personalized iiidea.
This is the primary purpose of Riiiver — to enable users to create compelling, personalized functions and experiences without needing to do any coding, and allow other Riiiver users to connect with those functions and experiences while building their own.
About “iiidea” and “Pieces”
- The smallest functioning parts are called “Pieces.”
- The specific user experience that is formed when several Pieces are connected is called an “iiidea.”
By connecting three Pieces — a ‘T’, ‘S’, and ‘A’ Piece — users can design and create iiidea without needing to code at all.
- T: Trigger Piece → The Piece operating as the cue to begin to execute an iiidea.
- S: Service Piece → The Piece providing the service that will deliver whatever the T Piece requested (e.g. weather information).
- A: Action Piece → The Piece that outputs whatever was requested by the T Piece and delivered by the S Piece.
The easiest way to think about the differences between T, S, and A Pieces is to categorize them like this.
Think about how your products and services can be broken down into a Piece or Pieces that fit these categories. Once you’ve uploaded a Piece to the Riiiver environment, users should find this T, S, A structure conducive to imagining brand new experiences that connect them to you and back again.