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

Before-and-after illustration of the I9 Shop floating badge changing from a wide 180 × 70 px container to a taller 100 × 200 px purple container.

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.

  1. 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.
  2. I9 Shop Badge Status: Active
    I enabled the badge so visitors could see it on the homepage.
  3. I9 Shop Badge Type: Image Badge
    I selected Image Badge to display the app’s screenshot instead of a text announcement.
  4. I9 Shop Badge Image
    I uploaded a vertical screenshot of the I9 Shop mobile interface, showing its storefront and industrial products.
  5. I9 Shop Background Color: Enabled
    I added a dark purple background to distinguish the badge from the website’s light background.
  6. I9 Shop Background Opacity: 100%
    Full opacity gives the badge a solid, clearly visible background.
  7. I9 Shop Image Fit: Contain
    This keeps the entire screenshot visible without stretching or cropping it.
  8. I9 Shop Position: Bottom Left
    I placed the badge in the bottom-left corner, away from the chat controls on the right.
  9. I9 Shop Horizontal Margin: 20 px
    This creates a gap between the badge and the left edge of the screen.
  10. I9 Shop Vertical Margin: 90 px
    This raises the badge above the bottom edge to help separate it from other floating controls.
  11. 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.
  12. 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.
  13. I9 Shop Padding: 4 px
    This adds a small amount of space between the screenshot and the container’s edges.
  14. I9 Shop Border Radius: 8 px
    Rounded corners help the badge match the website’s design.
  15. 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.
  16. I9 Shop Destination Page
    The badge links to I9 Shop — Android App for Industrial Commerce, where visitors can learn about the Android app.
  17. I9 Shop Open in New Tab: Enabled
    Visitors can open the project page while keeping the homepage available.
  18. I9 Shop Close Button: Enabled
    Visitors can dismiss the badge if they need more space to read the page.
  19. 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.
  20. I9 Shop Close Behavior: Session Only
    I selected session-based dismissal rather than the longer-lived cookie option.
  21. I9 Shop Visibility: Front Page Only
    The badge promotes the app on the homepage without appearing on every page.
  22. 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.

SettingValue
Badge TypeImage Badge
ImageI9 Shop project screenshot
PositionBottom Left
Horizontal / Vertical Margin20 / 90 px
Desktop Size180 × 70 px
Mobile Size141 × 75 px
Background ColorOff
Image FitContain
Padding4 px
Border Radius8 px
Link TypeExternal URL
Open in New TabEnabled
Close ButtonEnabled
Close BehaviorSession only
VisibilityFront 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.

How to Fix AI Engine’s “No Credits Remaining” Error in WordPress: Billing and cPanel Logs

 

Why Kia AI Assistant says “You have no credits remaining”

Kia AI Assistant uses an external AI service to generate replies. When that service returns an insufficient-credit error, the chatbot cannot answer—even though the WordPress website and AI Engine plugin remain active.

Visitors may see:

“Oops! Something went wrong on the server.”

This message alone does not identify the cause. The underlying error must be checked in the server logs.

Where to check error logs in cPanel

Two places can help:

  1. cPanel → Metrics → Errors
    This displays recent web-server errors. It may not include the PHP error that explains the chatbot failure.
  2. cPanel → File Manager → public_html → error_log
    If PHP logging is configured to use this file, open it and check the latest entries for AI Engine, OpenAI, or insufficient_quota. For a site installed in a subfolder or a separate domain directory, check that site’s document root instead.

A relevant entry may look like:

AI Engine: OpenAI: You have no credits remaining.

The log location depends on your hosting configuration. If no error_log file appears, ask your hosting provider where PHP errors are recorded. Do not enable public error display on the live website.

How to restore replies

  1. Check the AI provider’s billing dashboard for available credit, payment issues, and usage restrictions.
  2. Confirm that AI Engine uses the API key from the intended organization and project.
  3. If you replace the key, save the settings and confirm that the chatbot uses the updated connection.
  4. Open the public website and send a short test message.
  5. If it still fails, check the newest log entries to identify the current error.

How to avoid unexpected interruptions

Check usage and billing regularly. Enable balance notifications or recharge options where your provider supports them, and configure appropriate usage limits in AI Engine.

The plugin’s usage estimates and “active” status do not confirm your provider’s remaining balance.

Protect your credentials and logs

Never publish API keys, private billing information, or complete server logs. Share only relevant, redacted error messages.

Ensure that log files inside public_html cannot be downloaded through a public URL. Ask your hosting provider to restrict access or store logs outside the public directory. Revoke and replace any exposed API key.

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.

Designing Apps for iPhone Duo

Designing Apps for iPhone Duo

Introduction

Designing applications for iPhone Duo introduces new opportunities to create flexible, immersive, and intuitive user experiences. This guide explores the design principles behind iPhone Duo and explains how to adapt existing iOS applications to its different screen sizes, orientations, and folding configurations.

The goal is to create applications that feel natural and consistent, regardless of how the device is used.

1. Understanding the iPhone Duo Form Factor

When closed, iPhone Duo is compact, familiar, and comfortable to hold. When opened, it reveals an expansive, immersive display that provides additional space for applications and content while maintaining the portability of a smartphone.

The device supports several configurations:

  • Closed: A compact smartphone experience.
  • Book Mode: A partially folded display resembling an open book.
  • Laptop Mode: A partially folded device resting on a table, with the upper display facing the user.
  • Standing Mode: A self-supporting configuration that rests on the device’s edges.
  • Fully Open: An expanded display for immersive content and multitasking.

These configurations allow users to interact with applications in different ways depending on their environment and preferences.

Applications should adapt naturally to these configurations without requiring users to learn different navigation systems.

2. Designing for the Outer Display

When closed, iPhone Duo features a display that is wider and shorter than a traditional iPhone screen. To maximize available vertical space, controls normally positioned at the top or bottom of the interface move to the right edge of the display.

This arrangement improves accessibility and creates an uninterrupted content area.

The vertical control region accommodates several interface components, including:

  • Tab bars
  • Application toolbars
  • Navigation buttons
  • Status information
  • Dynamic Island
  • Live Activities

The Dynamic Island expands vertically when Live Activities appear.

Moving these elements to the side creates additional space for content while keeping essential controls within comfortable reach.

The same design approach extends to the inner display, where controls can also move to the edges to maximize usable space.

3. Adapting to Folded Configurations

When iPhone Duo is partially folded, the display curves through its central region. This curved area introduces challenges for readability and touch interactions.

To maintain usability, interface elements should automatically adjust their positions.

Text and images should move away from the central curve to improve readability. Buttons and other interactive elements should shift toward accessible areas where users can interact with them comfortably.

The fold can also function as a natural visual divider between different sections of an application.

Portrait Orientation

When the device is partially folded in portrait orientation, interactive controls should move toward the lower half of the display.

This positioning improves accessibility while allowing the device to remain stable on a surface.

The objective is to preserve usability across different physical configurations without introducing unnecessary complexity.

4. Supporting Multitasking with Split View

iPhone Duo introduces a multitasking experience that allows two applications to operate side by side.

Users can drag an application toward the edge of the screen to activate Split View. The display is then divided into two equal sections, each functioning independently.

This arrangement allows users to continue working in one application while interacting with another.

Control Placement in Split View

In Split View, application controls move toward the outer edges of the display.

For example, when an application occupies the left half of the screen, its controls appear along the left edge.

This arrangement keeps controls accessible while preventing them from interfering with the central folding region.

Applications should remain functional and responsive when operating within either half of the display.

5. Picture-in-Picture and Dynamic Resizing

Picture-in-Picture allows users to continue watching video content while interacting with another application.

On iPhone Duo, a video can be positioned at the top of the screen. The active application automatically resizes vertically to occupy the remaining space.

When the device is partially folded, the video can expand to fill one half of the display.

Applications must therefore support dynamic resizing as available screen space changes.

Layouts should respond immediately to these adjustments without disrupting content or navigation.

6. Building Adaptive Application Layouts

Applications should accommodate different screen configurations without requiring a separate interface for every folding position.

The recommended approach is to focus on two primary size classes.

Compact Width

Compact width applies to the outer display.

Applications should prioritize efficient use of space, accessible controls, and clear content presentation.

Regular Width

Regular width applies to the expanded inner display.

Applications can take advantage of the additional horizontal space to display more information simultaneously.

Recommended Design Practices

Avoid relying on fixed screen widths, device-specific breakpoints, or measurements tied to a particular display.

Instead, build flexible interfaces using:

  • Layout margins
  • Horizontal safe area insets
  • Adaptive containers
  • Resizable interface components
  • Size-class-based layouts

Applications that already follow these principles should require fewer adjustments to support iPhone Duo.

The fundamental objective is to make interfaces freely resizable.

7. Optimizing Hands-Free Experiences

Partially folded configurations create opportunities for hands-free interactions.

For example, when iPhone Duo rests on a table in a laptop-like position, media content can appear on the upper display while interactive controls occupy the lower display.

This arrangement is particularly useful for video playback and other media-focused experiences.

However, specialized layouts should preserve the same controls and general navigation structure available in other configurations.

Essential functionality should never depend exclusively on a particular folding position.

Users should be able to access the same features whether the device is open, closed, or partially folded.

8. Managing Vertical Controls

Most iPhone Duo configurations position application controls along the side of the display.

An exception occurs when the inner display is used in portrait orientation, where horizontal control bars remain appropriate because sufficient vertical space is available.

The vertical control region may also contain system elements such as Live Activities and status information.

When available space becomes limited, application controls automatically collapse into an overflow menu.

Toolbar Behavior

Existing toolbar controls can generally be mapped to the new layout.

Controls originally positioned at the top of an application move toward the upper portion of the vertical control region.

Controls originally positioned at the bottom move toward its lower portion.

Tab bars remain aligned with the bottom.

However, not every interface component should move to the side.

Wide elements, including text buttons and segmented controls, should remain within the navigation bar when they cannot fit comfortably in the vertical control region.

This approach preserves readability and usability.

9. Designing Asymmetrical Interfaces

Moving controls to the side creates asymmetrical layouts.

Traditional iPhone interfaces often center content relative to the entire display.

On iPhone Duo, this approach may cause content to overlap with side controls.

Most content should therefore be positioned relative to the available safe area rather than the full display width.

Using horizontal safe area insets allows this adjustment to occur automatically.

Full-Screen Content

Some interfaces can remain centered across the entire display.

This approach works particularly well for immersive visual experiences that do not require scrolling.

However, interactive elements must remain clear of side controls.

Combining Layout Approaches

Applications can also combine full-width visual elements with inset content.

For example, a background image or header can extend across the entire display while foreground content remains within a safe, scrollable area.

All interactive elements should remain inside the accessible content region.

This prevents controls from being obscured or becoming difficult to use.

10. Optimizing Applications for the Inner Display

The expanded inner display should offer more than a stretched version of a traditional iPhone interface.

Applications should use the additional space to improve navigation, content organization, and productivity.

Three approaches are particularly useful.

Approach 1: Split Views

Split views allow multiple levels of an application’s navigation hierarchy to appear simultaneously.

For example, a list of items can appear on one side while the selected item’s details appear on the other.

The underlying navigation hierarchy should remain consistent between the inner and outer displays.

Users should not encounter different functionality simply because the device has been opened or closed.

Approach 2: Adaptive Multi-Column Layouts

Applications can reorganize their content when additional horizontal space becomes available.

For example, a vertically stacked layout can transform into a two-column arrangement.

This approach is useful for applications displaying media, product collections, or structured information.

The content remains the same, but its presentation adapts to the available space.

Approach 3: Sidebar Navigation

Applications using tab bars can convert them into sidebar navigation on the inner display.

This approach is particularly effective for information-dense applications.

A sidebar provides persistent access to navigation categories while leaving more room for detailed content.

However, sidebar navigation is not necessary for every application.

The appropriate solution depends on the application’s information structure and user experience requirements.

11. Adapting Sheets and Modal Interfaces

Sheets also adapt to the different configurations of iPhone Duo.

On the outer display, sheet controls move to the side by default.

Developers can disable the vertical bar when the content benefits from retaining horizontal controls.

This option works particularly well for sheets containing only one toolbar button.

In this configuration, the sheet stops before reaching the front-facing camera, and the status bar adjusts its position.

Inner Display Behavior

On the inner display, sheets use standard horizontal bars in both portrait and landscape orientations.

When the device is partially folded, sheets shift away from the central folding region.

This prevents important controls from appearing in areas that are difficult to interact with.

12. Avoiding Interactive Elements in the Fold

The central fold can make buttons and other interactive elements difficult to tap.

To address this challenge, system components automatically reposition interactive elements when the device is partially folded.

This behavior is supported by components such as:

  • Sheets
  • Alerts
  • Menus
  • Toolbar buttons
  • Other standard interface controls

Using native system components allows applications to benefit from this behavior without requiring extensive custom implementation.

The general principle is to keep interactive elements outside the curved region whenever possible.

Scrollable content, however, does not necessarily need to avoid the fold.

13. Maintaining a Consistent User Experience

Users may frequently open, close, and reposition iPhone Duo while interacting with an application.

The interface should respond smoothly to these transitions.

Navigation should remain predictable, and application functionality should remain consistent across configurations.

A user who begins a task on the outer display should be able to continue that task after opening the device.

Similarly, closing the device should not introduce unnecessary navigation changes or remove access to important features.

Adaptive design should improve the experience without making the application feel like a different product.

14. Key Design Recommendations

Successful iPhone Duo applications should follow several fundamental principles.

Prioritize adaptive layouts. Design interfaces that respond naturally to changes in available screen space.

Use size classes. Focus on compact and regular width configurations instead of device-specific dimensions.

Respect safe areas. Keep essential content and interactive elements away from system controls and difficult-to-reach regions.

Support flexible resizing. Ensure applications respond smoothly to Split View, Picture-in-Picture, and folding transitions.

Use native components. Take advantage of built-in interface behaviors, including automatic fold avoidance.

Optimize expanded layouts. Use additional screen space for multi-column content, split views, and sidebar navigation when appropriate.

Preserve consistency. Maintain the same core functionality and navigation hierarchy across all device configurations.

Conclusion

iPhone Duo introduces a new approach to designing applications for foldable smartphones.

Its combination of compact and expanded displays, flexible folding configurations, side-mounted controls, and multitasking capabilities creates opportunities for more adaptable user experiences.

The most effective applications will not rely on separate designs for every physical configuration.

Instead, they will use responsive layouts, native interface components, and consistent navigation patterns to adapt naturally as the device changes shape.

By embracing flexible resizing, thoughtful control placement, and adaptive content organization, developers can create applications that feel intuitive and fully integrated with the iPhone Duo experience.

Repeated AdSense Rejections Led Me to Rethink My WordPress Content

Illustration of Kia at a laptop, surrounded by website pages and error notifications, reflecting the frustration of repeated AdSense rejections.

A developer working through website setbacks at a laptop.

Several years ago, I built my first website in WordPress. I created pages, added content, and gradually worked on the site until it felt more complete. At the time, I wasn’t publishing blog posts. Everything went into pages.

The website took much longer to finish than I expected. When I finally decided to try Google AdSense, I hoped it would be the next step forward. Instead, my application was rejected again and again.

Each rejection was frustrating. I had already spent so much time building the site, and I struggled to understand what I needed to change.

The advice that made me feel I had to start over

A friend who worked in web development looked at my situation and suggested that I publish my article content as posts rather than keeping everything in pages. He thought I would need to recreate the content and delete the old versions.

That was difficult to hear. The thought of rebuilding work that had already taken so long left me discouraged. I wanted to improve the website, but I didn’t want to copy everything manually and begin again.

Looking back, there were two separate questions: how to organize my WordPress content, and why AdSense had rejected the site. Changing the first would not necessarily answer the second.

How AI helped me find a simpler approach

Before committing to a complete rebuild, I asked an AI assistant whether there was an easier way to turn existing pages into posts.

It suggested a WordPress plugin called Post Type Switcher.

The plugin lets you change an existing item’s content type, including converting a page into a post. It also supports bulk changes. That meant I had an alternative to manually recreating each article. See the plugin’s official description.

I used it to convert many of my pages into posts. For me, its value was practical: it made a task that had felt overwhelming much more manageable.

Website content cards being reorganized into a clear article collection.

What this taught me about pages, posts, and AdSense

There is an important correction to the advice I originally received: AdSense does not require you to publish your content as WordPress posts rather than pages. Google’s published requirements focus on original, useful content, policy compliance, and a website that visitors can navigate. They do not specify a WordPress content type. Read Google’s eligibility requirements and site-readiness guidance.

Posts can help organize a growing collection of articles through categories and a blog archive. Pages still have a useful role for content such as About, Contact, and service information.

The right choice depends on what the content is for. Turning a page into a post does not improve the writing by itself, and it does not guarantee AdSense approval.

I also cannot conclude from this experience that using pages was the reason for my rejections. What I can say is that the plugin helped me reorganize existing content without manually recreating it.

What I recommend before converting content

If you are in a similar situation, Post Type Switcher may be worth considering. Start with a backup and test one item on a staging copy before making bulk changes. The plugin’s documentation notes that conflicts with other plugins can occur. Plugin documentation.

After a conversion, check these details:

  • Layout: Does the article still display correctly, especially if it uses a page builder?
  • Address: Has the URL changed? If so, redirect the old address to the new one.
  • Navigation: Do menus and internal links still lead to the right place?
  • Organization: Does the article appear in the intended category and blog archive?

You do not need to convert every page. Choose the content that belongs in your article collection, and keep other pages where they make sense.

A small tool made a difficult task feel possible

The most useful part of this experience was discovering that I had another option. I could reorganize what I had already written instead of assuming I needed to rebuild everything.

AI helped me find the tool, and Post Type Switcher helped me carry out the change. The experience also reminded me to check the reasoning behind advice, even when it comes from someone with more experience.

If your WordPress articles are currently stored as pages, this plugin could save you some work. If your goal is AdSense approval, review the quality and usefulness of the whole website as well. Content organization is one part of that work.

Blog posts