updated content: placed examples before FAQs. Removed repeated articles. updated assest

Author: mrdavidorok

docs/ff-concepts/adding-customization/build-iot-app.md

@@ -31,8 +31,9 @@ This article explains how to configure custom routing logic for users after they
     The **Persist** setting retains the value locally on the device until the app is uninstalled. It will reset on every refresh when testing in a web browser.
     :::
 
-    ![](../assets/20250430121414406250.png)
-    ![](../assets/20250430121414639307.png)
+    ![](imgs/20250430121414406250.png)
+
+    ![](imgs/20250430121414639307.png)
 
 **Add a User Field for Admin Check**
 
@@ -41,8 +42,9 @@ This article explains how to configure custom routing logic for users after they
 
     This allows conditional routing based on the admin role.
 
-    ![](../assets/20250430121414890408.png)
-    ![](../assets/20250430121415192057.png)
+    ![](imgs/20250430121414890408.png)
+
+    ![](imgs/20250430121415192057.png)
 
 **Configure Initial Pages**
 
@@ -56,7 +58,7 @@ This article explains how to configure custom routing logic for users after they
   **Logged In Page** is used when a user is already authenticated.
   :::
 
-  ![](../assets/20250430121415472919.png)
+  ![](imgs/20250430121415472919.png)
 
 **Define Actions on the Checkup Page**
 
@@ -69,9 +71,11 @@ This article explains how to configure custom routing logic for users after they
   - If `FALSE`:  
     - Add action: **Navigate To** `LoginPage`, disable **Back Navigation**, then **Add Terminate**.
 
-    ![](../assets/20250430121434550471.png)
-    ![](../assets/20250430121434823464.png)
-    ![](../assets/20250430121435145067.png)
+    ![](imgs/20250430121434550471.png)
+
+    ![](imgs/20250430121434823464.png)
+
+    ![](imgs/20250430121435145067.png)
 
 2. **Check If User Is New (First Time Login)**
 
@@ -81,7 +85,7 @@ This article explains how to configure custom routing logic for users after they
     - If `TRUE`:  
       - Add action: **Navigate To** `OnboardingPage`, disable **Back Navigation**, then **Add Terminate**.
 
-      ![](../assets/20250430121435792377.png)
+      ![](imgs/20250430121435792377.png)
 
 3. **Check If User Is an Admin**
 
@@ -94,7 +98,7 @@ This article explains how to configure custom routing logic for users after they
   - If `FALSE`:  
     - Navigate to `UserHomePage`, disable back navigation, then **Terminate**.
 
-  ![](../assets/20250430121436144376.png)
+  ![](imgs/20250430121436144376.png)
 
 **Update `firstTime` After Onboarding**
 
@@ -105,14 +109,15 @@ This article explains how to configure custom routing logic for users after they
     3. Add action: **Update Local State** > `firstTime` → set value → `False`.
     4. Add navigation: **Navigate To** `CheckupPage`, disable back navigation.
 
-    ![](../assets/20250430121436460665.png)
-    ![](../assets/20250430121436751661.png)
+    ![](imgs/20250430121436460665.png)
+
+    ![](imgs/20250430121436751661.png)
 
 :::tip
 You can reuse the `CheckupPage` to add more advanced routing conditions, such as checking if the user has completed their profile or enabled certain settings.
 :::
 
 To skip onboarding for admins as well, extend your logic by nesting onboarding logic inside the admin check condition.
 
-![](../assets/20250430121437067417.png)
+![](imgs/20250430121437067417.png)