Struklio Update 1.0.3

Struklio version 1.0.3 is our third product update since launch.

This update focuses on three important areas: fixing dynamic screen scrolling, improving the payment setup experience, and introducing the product analytics we need to understand how people actually use Struklio.

Fixing Cut-Off Content on Service Business Screens

We found an issue affecting the Service Business template where users could not always scroll to the bottom of a screen.

The issue was most visible in the Popular Categories grid. The screen could show several category rows and then cut off part of the content directly above the bottom navigation bar, even though more categories existed below.

The problem was more complex than one screen or one scrolling container. The same underlying behavior existed in three different parts of Struklio:

• The live or exported app
• The Builder’s Review Mode
• The drag-and-drop Builder canvas

The category grid loads its real content from the backend after the component has already been rendered. Before that data is available, the Builder uses an estimated component height.

When the real number of categories exceeded that estimate, the component could become restricted by the original height. An internal scrolling container also prevented the outer page from expanding naturally.

We removed the unnecessary internal scrolling behavior and changed the component so it grows according to its actual content.

We also improved Review Mode so dynamic components are no longer limited by fixed design-time height estimates. This makes the preview more accurately reflect the real published application.

Inside the Builder canvas, dynamic components can now report their actual rendered height. The canvas uses this value when calculating how far the user can scroll and where components can be moved.

The result is that users can now reach all of the content on these screens, even when the real data requires more space than the original layout estimate.

A Better Way to Connect Payments

We have also changed how Stripe payments are configured in Struklio.

Previously, Stripe was configured separately inside each app by manually entering Stripe keys.

That structure did not match how businesses normally operate. A business usually has one Stripe account, even when it manages several applications.

It also created a practical problem: app-specific settings could be reset when a new project was created from a template. This meant payment configuration could be lost or require the same information to be entered repeatedly.

In version 1.0.3, Stripe is connected once at the Struklio account level using Stripe Connect.

Users now open their main account settings and select Connect with Stripe. Stripe’s own hosted onboarding flow handles the account connection, so secret API keys are no longer entered into the Struklio client.

Once connected, the same Stripe account can be used by all applications under that Struklio account.

We have also improved the way payment status is displayed. Struklio can now distinguish between a payment account that is not connected, an account whose setup is incomplete, and an account that is fully connected and ready to receive payments.

If Stripe onboarding has not been completed, the checkout flow is blocked and the user is shown a clear message instead of allowing the payment attempt to continue incorrectly.

Understanding How Struklio Is Used

Until now, we have had considerably more visibility into how people use the Struklio website than how they use the actual application.

That is changing with this update.

We are introducing product analytics through PostHog so we can understand the main actions users take inside Struklio.

This includes questions such as:

• Do users create a project after opening the app?
• Which templates are selected most often?
• Do users open their generated applications?
• Do they enter the Builder?
• Do they test their projects in Review Mode?
• At which point do users stop progressing?
• Which features are actively used?
• How many app projects are being created?

This is basic product data, but it is essential for making better decisions.

Without it, we can see downloads and website activity, but we cannot reliably understand what happens after someone enters the product.

The purpose of this analytics layer is not simply to collect more numbers. It is to identify where the experience is unclear, which features create value, and where users encounter friction.

This information will support everyday product development, future updates, investor discussions, social media reporting, press communication, and eventually the people who join Struklio as the company grows.

The first version will focus on understandable, actionable events rather than collecting everything possible. The goal is to create datasets that help us make decisions, not dashboards filled with numbers that have no practical use.

Continuing to Improve the Foundation

Version 1.0.3 is another step toward making Struklio more reliable and measurable.

The scrolling fix improves the relationship between dynamic data, the Builder, Review Mode, and the final application.

Stripe Connect gives payment configuration a structure that better reflects how real businesses work.

Product analytics will help us understand what users are doing instead of relying only on assumptions.

There is still a significant amount of work ahead, but every update gives us a stronger foundation for the next one.