MyJackfruit

Help
Browse topics · Finishing

Finishing

← Finishing

What should the first page of my app say, and does it need Help, Contact and privacy pages?

Short answer

Say what it is, for whom, and what to do first. Help and Contact are your choice; for privacy, ask someone who knows the law.

Deeper

Also asked:

Should my app have a Help or Contact page before going live? It is your choice: GilbPlatform does not check for them. A Help page is one more page your AI builds. A contact form that sends to an outside form service or e-mail service does not work in a published app today.

This answer is advice. GilbPlatform does not check whether your app has a Help, Contact or privacy page before it goes live: it checks the kinds of file, their size and that no file holds a secret key, not what your pages say.

The first page. A first-time visitor is someone who opens your app with no one there to show them how. Many first pages say, in a few short lines, what the app is, who it is for and what to do first, with one clear button for that first act, for example to book a time or to sign in. If your app signs people in, you could say that they sign in with a code sent to their e-mail, so a newcomer knows what to expect. Give your own words to Kai-Zen, the planning agent; the answer Who writes the text in my app, and can I change it myself? tells more.

What your AI does already. Agent.Coder, the agent that writes your app's code, follows written rules that help a newcomer find their way. The main menu, unless you describe another: a button at the top shows where you are, and a large panel shows the main sections. It lists only what is built, and what you name as coming, so no one is sent to an empty page. Buttons are named by what they do, such as Save, never OK or Yes. Rules cannot tell you whether your app is easy; people can. The answer How do I make my app easy for a first-time visitor? shows how to watch someone new try it.

A Help page. GilbPlatform and GilbApp have no help pages for your app; a Help page is one more page of your app, which your AI builds like any other. You could start with the questions your first testers asked.

A Contact page. GilbPlatform has no ready-made contact form. GilbPlatform sends its own e-mails, such as the sign-in code, but it has no part your app can use to send e-mails or text messages. A published app today reaches only its own files and GilbPlatform's own addresses, so a form that sends to an outside form service or e-mail service does not work in your published app today. What can work today, and what is blocked, is in Can my website have a contact form? How to answer your users, and where they write when something is wrong has its own answer.

A privacy page. Whether your app needs one depends on what it collects and on the law where you and your users are; this help gives no legal advice. MyJackfruit's Privacy page does not name apps that others build, so it does not say what your app does with data: that is for your own page. Your AI can draft one for you to check; the answer Do I need a privacy page and a cookie banner? tells more. Ask someone who knows the law where you live. Whether you must say who runs your app is in Do I need terms of use, and must I say who runs my app?

This answer is written for a computer screen.

Source: Standards read from GilbPlatform on 13 November 2026: Agent.Coder (Contextual: Rule_Code_default-menu for the app's main menu; Rule_Code_design-guide). GilbPlatform 0fc5a548 (https://id.gilb.com/version, read 13 November 2026): workers/publish-ingest/src/checks.ts:125-160 (what a publish checks: names, kinds, size, index.html, secrets; nothing reads what the pages say). https://myjackfruit.com/privacy/ (read 13 November 2026; last updated November 11, 2026): covers myjackfruit.com, GilbApp and the vaults, not apps others build. Live help pages, sentences shared: How do I make my app easy for a first-time visitor? (the main-menu rule; buttons named by what they do); Can my website have a contact form? (no ready-made contact form; no part your app can use to send e-mails); Do I need a privacy page and a cookie banner? (the Privacy page does not name apps others build); Who writes the text in my app, and can I change it myself?; Can my app have its own users who sign in? (sign-in by a code sent to their e-mail).

Checked against GilbApp d529620.