MyJackfruit

Help
Browse topics · Keeping it running

Keeping it running

← Keeping it running

Why is my app slow, and is it slower on phones or a weak connection?

Short answer

Pictures too big, too many reads or a weak connection can slow it; phones can be slower. Tell your AI which screen, and how slow.

Deeper

Also asked:

How do I check that my app is fast enough before going live? Ask your AI to measure the screens people will use most and show you the seconds each takes and how many requests it sends; try it yourself with the connection slowed to 3G. If a screen feels slow, say so before you say yes to going live.

My live app became slow. What now? If GilbApp is slow too, see Is GilbPlatform down? Where can I see if something is wrong? Otherwise measure the live address and tell your AI the numbers, which screen and since when; the fix goes live with your yes.

Yes, it can be slower on a phone or a weak connection. Google's page on inspecting network activity says the connection of the computer you build on "is probably faster than the network connections of the mobile devices of your users" (https://developer.chrome.com/docs/devtools/network, read 13 November 2026). That is why the speed rule Agent.Coder, the agent that writes your app's code, follows says to build for a phone on a mobile network first, and to measure on a phone-size screen with a slowed network too. An agent is your AI following one written procedure, its standing instructions, for one kind of work.

Things that can cause it:
- Pictures bigger than the screen shows. Google says anything larger just results in wasted bytes and slows down page load time (https://developer.chrome.com/docs/lighthouse/performance/uses-responsive-images, read 13 November 2026). See Do big pictures and videos make my app slow?
- Too many reads, that is, asks of a vault for records, one after another. The speed rule says a list reads its records in pages of up to 200, never one record at a time, and reads only what changed since last time. In one example in the rule, counted by a test on a stand-in platform, a screen sent 126 requests on the first visit and 126 again on a return visit, so every return visit started from zero.
- Waiting with nothing on the screen. The rule says to show the screen at once, show that it is updating, and fill in the rest when it comes.
- Heavy work that freezes the screen. The rule says to keep the screen free by splitting big work into small parts.
- GilbPlatform itself. If everything, also GilbApp, is slow at the same time, see Is GilbPlatform down? Where can I see if something is wrong?.

What to tell your AI. Say which screen, what you did, how many seconds it took, on which device and which connection (Wi-Fi or mobile), and whether it is slow every time or only the first time. Ask it to measure before and after its fix, as its speed rule asks, and to show you the numbers. The answer How do I tell my AI about a fault so it can fix it? shows how to describe it.

Try a weak connection yourself. In the Chrome browser's DevTools, Chrome's tools for looking inside a page, the Network panel has a menu that is set to No throttling; choose 3G there to make the connection slower on purpose, then reload the page (https://developer.chrome.com/docs/devtools/network, read 13 November 2026). The answer How do I make sure my app is fast, and how do I measure it? shows two checks for the live app, PageSpeed Insights and Lighthouse.

Before your app goes live. Ask your AI to measure the screens people will use most and show you the seconds each one takes and how many requests it sends. Its speed rule asks it to fill a speed table before and after any change it makes for speed, and says a speed claim without that table is not evidence. The rule also asks it to measure where people use the app, on the live address, so the full check comes once your app is live; before that, you could try it on your computer with the connection slowed to 3G, as above. If a screen feels slow to you, say so before you say yes to going live.

If your live app became slow. First check whether only your app is slow: if GilbApp is slow too, see Is GilbPlatform down? Where can I see if something is wrong?. Then measure the live address, as the answer How do I make sure my app is fast, and how do I measure it? shows, and tell your AI the numbers, which screen, and since when: since a change you put live, or bit by bit as more records were added. For screens with many records, the speed rule asks a list to read its records in pages of up to 200, and after the first read only what changed, so your AI can check the slow screen against that rule. The fix goes live like any change, with your yes and at the same address; see How do I update my app after it is live? If it stays slow and you think GilbPlatform is the cause, write to [email protected] with the address, the screen and the time.

This answer is written for a computer screen.

Source: Standards read from GilbPlatform on 13 November 2026: Agent.Coder (Contextual: Rule_Code_gilb-app-speed), Rule_Code_gilb-app-speed (RuleAppspeedPhoneFirst: build for a phone on a mobile network, keep the main thread free, measure on a phone-size screen with a slowed network; RuleAppspeedOneReadPerPage: pages of 200, never a per-row follow-up; RuleAppspeedChangesOnly; RuleAppspeedMeasureFirst: before and after, the Social Drafts example of 126 requests on first and return visits; RuleAppspeedVisibleWait). Chrome DevTools, Inspect network activity, throttling (https://developer.chrome.com/docs/devtools/network, read 13 November 2026). Chrome, Lighthouse, Properly size images (https://developer.chrome.com/docs/lighthouse/performance/uses-responsive-images, read 13 November 2026). Live help pages, sentences shared: Is GilbPlatform down? Where can I see if something is wrong?; How do I tell my AI about a fault so it can fix it? Rule_Code_gilb-app-speed (the rule's opening: measured where the person uses the app, on the real host; RuleAppspeedMeasureFirst: the speed table before and after, seconds and request count; RuleAppspeedOneReadPerPage; RuleAppspeedChangesOnly). Live help pages, sentences shared: How do I make sure my app is fast, and how do I measure it?; How do I update my app after it is live?; Is GilbPlatform down? Where can I see if something is wrong?

Checked against GilbApp d529620.