KiaApp — Smart Apps for an Easier Life
Meet KiaApp: smart, simple, and modern app solutions designed to make everyday life easier. This short introduction presents our vision of turning ideas into practical digital experiences that help people save time and get things done.
Renewing the I-9 web app and clearing the old copy in Chrome

To renew the web app on the live site, start in the host File Manager and open public_html/work/I-9. That folder is the one the address https://kiaapp.xyz/work/I-9/index.html reads. Delete the old files already in I-9, then upload the new zip and extract it in the same folder. After extracting, index.html must sit directly inside I-9, next to main.dart.js, flutter.js, and the assets folder. Keep the file name index.html. The site is set to open that name, so a renamed page such as webapplication.html is handed back as the same index.html.
When the upload is finished, open https://kiaapp.xyz/work/I-9/index.html. The new files can already be on the host while the window still shows the previous app: the blue buttons, the black video, and the old layout. The browser has saved that copy and keeps using it. Clearing the host folder does not clear the copy stored on the Mac.
On a Mac, press Command+Option+I and leave the developer tools open. Select Application in the top bar of the tools, then select Storage. The Storage page shows Clear site data for https://kiaapp.xyz/. Leave these boxes checked: Cache storage, IndexedDB, Local and session storage, Unregister service workers, and Cookies. Click Clear selected. The usage figure should drop to a few kilobytes. That removes the saved site data for this address.
The tools also have to stay open for the next step, because the command that throws away the saved page files appears only then. Look at the top of the Chrome window, above the tools. On the left side of the address bar there is a round arrow. That arrow is the reload button. Right-click the arrow. A short menu opens with three lines, and the third line is Empty Cache and Hard Reload. Click that line. Chrome downloads the pages from the host again, including the new main.dart.js, and the product poster can replace the old screen.
Right-clicking the address text opens a different menu, with Look Up, Cut, Copy, and Paste. Close that menu with Escape and use the round arrow instead. The Storage page also has no Empty Cache and Hard Reload line. Clear selected and the reload arrow are two separate actions, and both belong in this cleanup.
After the reload, the address should remain https://kiaapp.xyz/work/I-9/index.html. The renewed app shows a search field, the product poster with the generator, valve, and power station, the green WhatsApp button, and the row of social icons. If a normal window still shows the old screen, open a New Incognito Window from the Chrome menu and paste the same address there. The private window has no saved copy, so it shows whatever the host is serving now.
Making the I9 Shop Floating Badge More Visible with AnchorBadge

I added a floating badge to help visitors discover I9 Shop — Android App for Industrial Commerce. Initially, the app’s vertical screenshot appeared too small inside a short, wide container.
To improve visibility, I reduced the badge’s width, increased its height, and added a purple background. Here are the settings I used for the I9 Shop badge, one by one.
- I9 Shop Live Preview
I used the preview to check how the screenshot looked as I adjusted the badge. I also checked the actual website because the preview is approximate. - I9 Shop Badge Status: Active
I enabled the badge so visitors could see it on the homepage. - I9 Shop Badge Type: Image Badge
I selected Image Badge to display the app’s screenshot instead of a text announcement. - I9 Shop Badge Image
I uploaded a vertical screenshot of the I9 Shop mobile interface, showing its storefront and industrial products. - I9 Shop Background Color: Enabled
I added a dark purple background to distinguish the badge from the website’s light background. - I9 Shop Background Opacity: 100%
Full opacity gives the badge a solid, clearly visible background. - I9 Shop Image Fit: Contain
This keeps the entire screenshot visible without stretching or cropping it. - I9 Shop Position: Bottom Left
I placed the badge in the bottom-left corner, away from the chat controls on the right. - I9 Shop Horizontal Margin: 20 px
This creates a gap between the badge and the left edge of the screen. - I9 Shop Vertical Margin: 90 px
This raises the badge above the bottom edge to help separate it from other floating controls. - I9 Shop Desktop Size: 100 × 200 px
I changed the desktop dimensions from 180 × 70 px to 100 × 200 px. The taller, narrower container makes the mobile screenshot easier to recognize. - I9 Shop Mobile Size: 70 × 140 px
I used a smaller portrait container for screens up to 767 px wide, keeping the badge compact on mobile. - I9 Shop Padding: 4 px
This adds a small amount of space between the screenshot and the container’s edges. - I9 Shop Border Radius: 8 px
Rounded corners help the badge match the website’s design. - I9 Shop Link Type: External URL
I selected this option to enter the project page’s full address, even though the destination is on my own website. - I9 Shop Destination Page
The badge links to I9 Shop — Android App for Industrial Commerce, where visitors can learn about the Android app. - I9 Shop Open in New Tab: Enabled
Visitors can open the project page while keeping the homepage available. - I9 Shop Close Button: Enabled
Visitors can dismiss the badge if they need more space to read the page. - I9 Shop Close Button Style: Filled Circle
I chose a white close icon on a black background with 85% opacity so the control remains easy to identify. - I9 Shop Close Behavior: Session Only
I selected session-based dismissal rather than the longer-lived cookie option. - I9 Shop Visibility: Front Page Only
The badge promotes the app on the homepage without appearing on every page. - I9 Shop Save Settings
I clicked Save Settings, and the green “Settings saved!” message confirmed that the configuration was saved.
The updated portrait layout made the I9 Shop screenshot more visible while preserving its original proportions. The final check is to test the badge on a phone, verify its destination, and ensure it does not cover important content or buttons.
Adding a Floating Badge for I9 Shop to My WordPress Website

Adding a Floating Badge for I9 Shop to My WordPress Website
I wanted visitors to KiaApp to easily discover I9 Shop — Android App for Industrial Commerce. While checking the project’s visibility on my website, I reviewed the navigation settings and configured a floating badge using AnchorBadge.
Checking the website’s cache
I initially considered whether caching explained differences between the editor and the live website. WP-Optimize was installed but inactive, and I did not identify another active page-cache plugin. Hosting or CDN caching remained a possibility, but cache clearing was not confirmed.
Setting up the project badge
I configured AnchorBadge to display a project image in the bottom-left corner of the homepage. Clicking it would open the I9 Shop introduction page.
| Setting | Value |
|---|---|
| Badge Type | Image Badge |
| Image | I9 Shop project screenshot |
| Position | Bottom Left |
| Horizontal / Vertical Margin | 20 / 90 px |
| Desktop Size | 180 × 70 px |
| Mobile Size | 141 × 75 px |
| Background Color | Off |
| Image Fit | Contain |
| Padding | 4 px |
| Border Radius | 8 px |
| Link Type | External URL |
| Open in New Tab | Enabled |
| Close Button | Enabled |
| Close Behavior | Session only |
| Visibility | Front page only |
The Contain setting preserves the screenshot’s proportions. Because the image is tall, it appears small inside the wide badge area; a dedicated horizontal project graphic could make it easier to recognize.
Linking to I9 Shop
I set the badge’s destination to I9 Shop — Android App for Industrial Commerce. The page introduces the Android app and displays its storefront screenshot, app information, and download controls.
Saving and checking the result
The final step was to enable Badge Status and click Save Settings, then test the badge on desktop and mobile. The checks included confirming that it opened the correct project page and did not overlap other floating controls.
Adding the badge and adding a project to the Work dropdown are separate changes: each needs its own configuration and verification.
Site Assistant: Your Partner for AI and App Development

Site Assistant is designed to make AI and app development easier to understand and manage. As a digital project companion, it can help turn an initial idea into a clear plan, support development decisions, and assist with the everyday challenges of building a useful digital product.
One of its main advantages is convenience. Having an assistant alongside your project gives you a place to ask questions, explore ideas, and request explanations without constantly switching between separate resources. You can describe what you want to achieve in ordinary language and use the conversation to break larger tasks into smaller, manageable steps.
Its potential abilities include drafting interface text, suggesting page structures, explaining programming concepts, and assisting with code. When connected to appropriate project tools and permissions, it may also help investigate errors, review existing implementations, and prepare improvements for you to evaluate. The exact actions available depend on how Site Assistant is configured.
Another advantage is its usefulness throughout the development process. During planning, it can help clarify requirements and compare approaches. During implementation, it can support troubleshooting and explain technical choices. During refinement, it can help identify confusing wording, inconsistent interactions, and opportunities to improve usability.
For beginners, Site Assistant can make technical work more approachable through clear explanations and practical guidance. For experienced developers, it can reduce time spent on routine questions, repetitive writing, and initial drafts. By providing support within the project workflow, it can help users maintain momentum, explore solutions, and spend more time on decisions that shape the final product.
How I Restored Missing WordPress Submenus in My Redesigned Elementor Homepage
After redesigning my KiaApp homepage, I noticed that my header no longer displayed all the submenu links. I checked Appearance → Menus, but everything looked correct. The pages were there, and their parent–child relationships were properly arranged.
The problem was in how I had built the new header.
My redesigned homepage used an Elementor HTML widget with manually written navigation links. That header did not automatically load my WordPress menu. Changing the menu in WordPress therefore had no effect on those manually written links.
The solution was to connect the redesigned header to my existing Main Menu using a PHP snippet.
What Is a Snippet?
A snippet is a small piece of code that adds or changes a specific part of a website’s behavior.
I used the Code Snippets plugin to save and activate the PHP code without editing my theme’s files. In this case, the snippet acted as a bridge between WordPress’s saved menu and my custom Elementor header.
The fix required two separate pieces:
- PHP in Code Snippets: retrieves the WordPress menu and builds its navigation structure.
- HTML, CSS, and JavaScript in Elementor: provide the homepage design and menu interactions.
Understanding where each piece belongs was an important part of the process. The homepage code beginning with <script> belongs in Elementor’s HTML widget, rather than in a PHP snippet editor.
How the PHP Snippet Works
1. It intercepts Elementor’s widget output
The snippet uses this filter:
add_filter('elementor/widget/render_content', ...)
This lets it modify a widget’s HTML when Elementor renders it, before that output reaches the visitor’s browser.
2. It identifies the KiaApp HTML widget
The code checks that the widget is an HTML widget and that its content includes:
class="kia-site"
If those checks fail, it returns the content unchanged.
Although I selected Run everywhere in Code Snippets, the code only modifies matching HTML widgets. If I reused the same marker on another page, that widget could also be affected.
3. It retrieves Main Menu from WordPress
The snippet finds my saved menu with:
wp_get_nav_menu_object('Main Menu')
It then retrieves its items using:
wp_get_nav_menu_items($menu->term_id)
These items provide the labels, links, order, and parent relationships needed to rebuild the navigation.
If the menu cannot be found or contains no items, the snippet leaves the original homepage HTML unchanged.
4. It preserves the submenu hierarchy
WordPress stores a parent identifier for each menu item. The snippet groups items by that identifier and follows the relationships through the nested levels.
For example:
Services
AI
Core AI
Build Your First AI Agent
The original custom header contained only a small selection of links. Reading the saved WordPress hierarchy allowed the snippet to include the deeper submenu items too.
5. It builds desktop and mobile navigation
The snippet creates two versions from the same menu data.
On desktop, it builds dropdown panels. In my implementation, the item labeled Services receives a wider panel with columns for its immediate children.
On tablets and phones, it creates expandable sections using HTML’s <details> and <summary> elements. Visitors can open a category and continue into its nested sections.
This is custom rendering of the WordPress menu hierarchy. It does not automatically reproduce every theme-specific mega-menu setting.
6. It replaces the existing navigation sections
The snippet replaces these two sections in the rendered homepage:
.kia-desktop-nav
.kia-mobile-panel
The logo on the left, the “Let’s Talk” button, hero image, and other homepage sections remain in place.
The homepage’s CSS controls the menu’s appearance, while its JavaScript handles desktop hover and click behavior, keyboard controls, and mobile interactions.
Why the Original Links Still Appear in the Elementor Editor
The snippet does not permanently rewrite the HTML saved inside my Elementor widget. It modifies the output when Elementor renders that widget.
This means the saved code can still contain the original short list of links, while the published page displays the full menu retrieved from WordPress.
Those original links also provide a fallback if the snippet is disabled or cannot find Main Menu.
How I Installed the Fix
I added the PHP code in Snippets → Add New, selected PHP, chose Run everywhere, and saved and activated it.
Then I opened the redesigned homepage in Elementor, backed up the existing HTML, and replaced the HTML widget’s contents with the matching homepage code. After publishing, I checked the navigation on the published page.
The full submenu structure appeared while preserving the redesigned header.
Where I Manage the Menu Now
Each part has a specific responsibility:
| Part | Responsibility |
|---|---|
| Appearance → Menus → Main Menu | Menu labels, destinations, order, and nesting |
| PHP snippet | Retrieves the menu and builds the navigation HTML |
| Elementor homepage code | Homepage design and menu interactions |
I now manage navigation through Appearance → Menus → Main Menu, instead of editing both desktop and mobile link lists manually.
The snippet must remain active, and the menu must retain the name Main Menu, unless I update that name in the PHP code. My implementation also identifies the Services panel by its label, so renaming that item would require adjusting the corresponding condition.
If a menu change does not appear immediately, I clear the relevant website cache and check the published page again.
This experience helped me understand the difference between a header that merely looks like a WordPress menu and one that actually uses WordPress’s saved menu data.
The functions used to retrieve the menu are documented in the official WordPress references for wp_get_nav_menu_object() and wp_get_nav_menu_items().


