# IntentsKitGameRevisit

**Repository Path**: gorit/IntentsKitGameRevisit

## Basic Information

- **Project Name**: IntentsKitGameRevisit
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: Apache-2.0
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 4
- **Created**: 2025-07-09
- **Last Updated**: 2025-09-23

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# Revisiting to Frequently Used Features Based on the Intent Framework and Habit Recommendation Capability

## Overview
Based on the intent framework, this sample demonstrates how to use `@kit.IntentsKit` for intent sharing and use `InsightIntentExecutor` of `@kit.AbilityKit` for intent calls. Revisit to the game by utilizing parameters from intent calls.

## Preview

| Home page                                             | Game page                                             | Sharing Intent Display on the Celia Widget                                                                     | Revisit to the Game Page by Tapping the Intent Widget                          |
|-------------------------------------------------------|-------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|
| ![home page](screenshots/device/1_en.png "home page") | ![Game page](screenshots/device/2_en.png "Game page") | ![Sharing Intent Display on the Celia Widget](screenshots/device/3_en.png "Sharing Intent Display on the Celia Widget") | ![Revisit to the Game Page by Tapping the Intent Widget](screenshots/device/2_en.png "Revisit to the Game Page by Tapping the Intent Widget") |

Instructions:
1. Tap the widget of `mini game 1 or 2` to enter the game page. Upon entering, the `shareIntent()` API is called. The API execution status is displayed at the bottom of the page.
2. After the sharing intent is processed, it will be displayed in a widget in Celia Suggestions.
3. Tap the Celia widget to restart the sample application and return to the game widget.

## Project Directory

```
├──entry/src/main/ets
│  ├──common
│  │  ├──constants
│  │  │  └──CommonConstants.ets         // Common constant class
│  │  └──utils
│  │     ├──FileReader.ets              // File reading class
│  │     └──Logger.ets                  // Log class
│  ├──entryability
│  │  └──EntryAbility.ets               // Entry page of the application implemented via Ability
│  ├──entrybackupability
│  │  └──EntryBackupAbility.ets         // Backup Ability
│  ├──insightintents
│  │  └──IntentExecutorImpl.ets         // Intent call class
│  ├──model
│  │  └──DataModel.ets                  // Game model class
│  └──pages
│     ├──Index.ets                      // Home Page
│     └──PlayPage.ets                   // Detail Page
└──entry/src/main/resources            
   ├──base
   │  └──profile
   │     ├──backup_config.json          // Backup config
   │     ├──insight_intent.json         // Intent registration configuration
   │     ├──main_pages.json             // App UI list
   │     └──router_map.json             // Router config
   └──rawfile
      ├──game.json                      // Example of game information
      ├──shareIntent.json               // Example of sharing intent data
      └──shareIntent_en.json            // English Example of sharing intent data
```

## How to Implement
Refer to the `shareIntent` method in `PlayPage.ets` for the source code related to intent sharing. Refer to the `onExecuteInUIAbilityForegroundMode` method in `IntentExecutorImpl.ets` for the source code related to intent calls.
- Home page: Read game information from the `game.json` file, generate game widgets using `ForEach`, and use `navPathStack.replacePathByName` in the `onClick` event of the widget to navigate to the game page.
- Game page: The game page displays relevant information based on the navigation parameters.
- Intent sharing: The game page calls the `shareIntent` method in the `aboutToAppear` event to filter the intent data from the `shareIntent.json` data that has been read based on the game ID, and then calls `insightIntent.shareIntent` API to share the intent data.
- Intent call: In the `onExecuteInUIAbilityForegroundMode`, use `eventHub.emit` to broadcast events and pass the `entityId` (game ID) parameter. In `Index.ets`, use `eventHub.on` to listen for events and navigate to the game page by calling `navPathStack.replacePathByName`.
- For hot start, parameters are passed to the home page via `eventHub`. For cold start, the `onCreate` method is used to transfer `want` parameter to the home page using the `localStorage` object.
- In this example, the intent call does not involve too much service logic or UI logic. Instead, it simply passes relevant parameters to the service side through different channels, leaving the page navigation decisions to the service itself. The `onExecuteInUIAbilityForegroundMode` interface provides a `WindowStage` instance. You can use `windowStage.loadContent` to load a specific page. The application can choose a proper method based on the actual requirements.

## Required Permissions

### Dependencies
1. This sample depends on `@ohos/hvigor-ohos-plugin`.
2. If you are using a version of DevEco Studio that is later than the recommended version for this sample, please follow the prompts in DevEco Studio to update the hvigor plugin version.
3. You need to be connected to the internet to log in to your HUAWEI ID and accept the Celia Suggestions user agreement and privacy policy.

### Constraints
1. **Currently, the intent sharing and intent call tests cannot be completed independently by developers. You need to submit an acceptance application to the Huawei Intents Kit contact by email following the [Intents Kit Integration Process](https://developer.huawei.com/consumer/en/doc/harmonyos-guides/intents-habit-rec-dp-self-validation). The contact person will assist you to complete the test and acceptance**.
2. This sample is only supported on Huawei phones running standard systems.
3. The HarmonyOS version must be HarmonyOS 5.0.5 Release or later.
4. The DevEco Studio version must be DevEco Studio 5.0.5 Release or later.
5. The HarmonyOS SDK version must be HarmonyOS 5.0.5 Release SDK or later.