add tapps

tearust · Dec 17, 2023 · 628d89d · 628d89d
1 parent 86d4dc8
commit 628d89d
Show file tree

Hide file tree

Showing 6 changed files with 61 additions and 5 deletions.
diff --git a/docs/_2_user_manual/Pasted image 20231217145641.png b/docs/_2_user_manual/Pasted image 20231217145641.png
diff --git a/docs/_2_user_manual/_1_TAppStore_1_tapps.md b/docs/_2_user_manual/_1_TAppStore_1_tapps.md
@@ -1,3 +1,29 @@
-# TAppStore-TApps list
+# Tea AppStore-TApps list
 
 Coming soon...
+
+## List of TApps
+
+## Set spending limit
+
+To grasp the concept of a **Spending Limit**, please refer to the [TApps](../_5_tapps/README.md#tapps) section.
+
+If you attempt to launch a TApp before setting the spending limit, you will be prompted to establish one. Subsequently, you will need to return to the TApps list and relaunch the desired TApp.
+
+Exercise caution when setting the spending limit, ensuring it is a reasonable value. The spending limit serves to safeguard consumers from potential errors. Should a TApp attempt to exceed the spending limit you've set, the transaction will be rejected.
+
+## Launching a TApp
+
+Once you have set an adequate spending limit for a TApp, click to launch it.
+
+For mobile users (Metamask browser), you may observe a "redirecting...." message between TAppStore and the TApp you are launching. This is normal; simply wait a few seconds, and the TApp will launch in your browser.
+
+Certain TApps are exclusively designed for web use. Attempting to launch them on a mobile device will result in an error message. Please utilize a computer to launch these specific TApps.
+
+## Creating new TApp on Web
+
+The "Create new TApp" button enables you to generate a new bonding curve token using existing TApp templates. This feature is available only on computer web platforms.
+
+![Pasted image 20231217145641.png](Pasted%20image%2020231217145641.png)
+
+Complete the form to generate a new TApp along with its corresponding bonding curve token. Once submitted, this TApp will be included in the TApps list, and its associated bonding curve token will be featured in the **Investments** section, allowing others to invest in it.
diff --git a/docs/_5_tapps/README.md b/docs/_5_tapps/README.md
@@ -4,7 +4,7 @@ TApps are rich decentralized applications that run on the TEA network. Due to th
 
 From the end-users perspective, two steps are needed before deploying any TApp for use:
 
-1. A spending limit for the TApp must be set. This ensures that a TApp can't spend more than what you've alloted for that TApp. As money is spent in the TApp, the spending limit is reduced. In this way it functions like an allowance that can be spent, with the end-user able to bump it up at any time.
+1. A spending limit for the TApp must be set. This ensures that a TApp can't spend more than what you've allocated for that TApp. As money is spent in the TApp, the spending limit is reduced. In this way it functions like an allowance that can be spent, with the end-user able to bump it up at any time.
 1. A node must be selected to run the TApp. Because of TEA's architecture, TApps are "hosted" in IPFS waiting for deployment. Because IPFS is just storage, the node that the end-user requests will download the compiled TApp binary from IPFS and execute in the node together with any data that the end-user provides.
 
 The list of available TApps is available through the [TEA Browser Wallet](TEA-Browser-Wallet.md). 

diff --git a/obsidian/_2_user_manual/Pasted image 20231217145641.png b/obsidian/_2_user_manual/Pasted image 20231217145641.png
diff --git a/obsidian/_2_user_manual/_1_TAppStore_1_tapps.md b/obsidian/_2_user_manual/_1_TAppStore_1_tapps.md
@@ -1,4 +1,34 @@
 
-# TAppStore-TApps list
+# Tea AppStore-TApps list
+
+Coming soon...
+
+## List of TApps
+
+## Set spending limit
+
+To grasp the concept of a **Spending Limit**, please refer to the [[_5_tapps/README#TApps|TApps]] section.
+
+If you attempt to launch a TApp before setting the spending limit, you will be prompted to establish one. Subsequently, you will need to return to the TApps list and relaunch the desired TApp.
+
+Exercise caution when setting the spending limit, ensuring it is a reasonable value. The spending limit serves to safeguard consumers from potential errors. Should a TApp attempt to exceed the spending limit you've set, the transaction will be rejected.
+
+## Launching a TApp
+
+Once you have set an adequate spending limit for a TApp, click to launch it.
+
+For mobile users (Metamask browser), you may observe a "redirecting...." message between TAppStore and the TApp you are launching. This is normal; simply wait a few seconds, and the TApp will launch in your browser.
+
+Certain TApps are exclusively designed for web use. Attempting to launch them on a mobile device will result in an error message. Please utilize a computer to launch these specific TApps.
+
+## Creating new TApp on Web
+
+The "Create new TApp" button enables you to generate a new bonding curve token using existing TApp templates. This feature is available only on computer web platforms.
+
+![[Pasted image 20231217145641.png]]
+
+Complete the form to generate a new TApp along with its corresponding bonding curve token. Once submitted, this TApp will be included in the TApps list, and its associated bonding curve token will be featured in the **Investments** section, allowing others to invest in it.
+
+
+
 
-Coming soon...
diff --git a/obsidian/_5_tapps/README.md b/obsidian/_5_tapps/README.md
@@ -4,7 +4,7 @@ TApps are rich decentralized applications that run on the TEA network. Due to th
 
 From the end-users perspective, two steps are needed before deploying any TApp for use:
 
-1. A spending limit for the TApp must be set. This ensures that a TApp can't spend more than what you've alloted for that TApp. As money is spent in the TApp, the spending limit is reduced. In this way it functions like an allowance that can be spent, with the end-user able to bump it up at any time.
+1. A spending limit for the TApp must be set. This ensures that a TApp can't spend more than what you've allocated for that TApp. As money is spent in the TApp, the spending limit is reduced. In this way it functions like an allowance that can be spent, with the end-user able to bump it up at any time.
 2. A node must be selected to run the TApp. Because of TEA's architecture, TApps are "hosted" in IPFS waiting for deployment. Because IPFS is just storage, the node that the end-user requests will download the compiled TApp binary from IPFS and execute in the node together with any data that the end-user provides.
 
 The list of available TApps is available through the [TEA Browser Wallet](TEA-Browser-Wallet.md).