A Jotform app is a link, and a link on a home screen is still a web page.
Jotform Apps gives you a URL, an embed code, and an app people can install from that URL. Jotform's help centre puts the delivery in one sentence: once your app is published, people can install it on their device for quick access or open it directly in their web browser. There is no build step in that sentence or anywhere near it, and nothing in the product makes a file you submit to a store. Where Jotform does spell out what a home screen shortcut is, in the guide to its Add to Home Screen form widget, it says the shortcut opens your form in the browser. Every claim about Jotform on this page comes from Jotform's help centre, read on 22 October 2026. If what you want is the app rather than the link, the plain version of that question is in build mobile app without coding.
This page covers what the Publish tab actually hands you, what happens to your submissions and your uploaded files if you leave, what Apple says about shipping a frame around a URL, and which pieces are worth rebuilding. One of those answers is more useful than the rest: your data comes out whole, in one ZIP, and Jotform documents how.
Start hereThe short version
Jotform calls them mobile apps. It never claims a build.
Jotform's guide to creating an app opens by saying Jotform Apps allows you to create mobile apps without coding, and the product pitch at the bottom of every Apps help page says web and mobile apps. Both are fair descriptions of what people get. The help centre also describes the delivery in one sentence: after your app is published, people can install it on their device for quick access or open it directly in their web browser. That is the whole shape of it.
So the migration question splits in two, and the halves are not equally hard. The front of a Jotform app is a hosted web page with an icon, a splash colour and a login wall, and a web page cannot be installed from a store. The back of it is Jotform Tables, your file uploads, your notification emails and your integrations, and all of that is reachable over HTTP from anything, including an app you build yourself. Most people who plan this well rebuild the front and keep paying for the back.
What does Jotform Apps actually publish?
A link, and some ways to hand the link around. The Publish tab of App Builder gives you three things, by Jotform's own description: your app link to copy and share manually, an email invitation, and a Share App panel for Facebook, WhatsApp, X and LinkedIn or a downloadable QR code. Jotform suggests inviting no more than ten people by email at a time. A separate Embed panel hands you an embed code, or a WordPress shortcode if that is what your site runs on. When somebody scans the QR code, the app opens on their device, which is to say it opens in their browser.
The link can be made to look like yours. Jotform documents an Organization Name and a Custom URL Slug that become part of the app URL, with one warning worth copying into your notes: changing the slug later changes the app URL too, so you have to tell your users and update any link you have already sent. Remove the slug and the URL reverts to Jotform's default format. On the Settings side you get an App Name and Icon, from an icon set or an uploaded image, and a Splash Screen whose customisation is a background colour, by picker or HEX code.
What is not there is the interesting part, so here is how I checked it rather than an assertion. I read five Jotform help articles end to end on 22 October 2026: creating and publishing an app, sharing an app, embedding an app in a website, changing the app name and icon, and how Jotform Apps differs from Jotform Mobile Forms. The words App Store, Google Play, iOS, Android, APK, TestFlight, progressive web app and native do not appear in the body of any of them. The only Apps article that names the App Store and Google Play is the push notification guide, where it is telling you to install Jotform's own Mobile App on your phone so alerts have somewhere to land.
Check yours
Which of these do you actually need?
Tick the reasons you wanted a phone app. The middle answer is what Jotform's own help centre documents, read on 22 October 2026. The last one is what the same job costs in an app you build and ship.
Nothing ticked yet. If the only honest answer is that a link feels less official than an app, keep the link and spend the money somewhere else.
What happens to your submissions and uploaded files?
They come out, and Jotform documents the button. In Account Settings there is a Data section with Download My Data. You create a report, pick a time frame or a preset range, then tick which kinds of data to include: form submissions, uploaded files, your form configurations, and AI Agent conversation history. Jotform packages the lot into a single ZIP file, which you download from the list or from the notification email it sends you. Attachments can also be taken on their own from Jotform Tables with Download Attachments, which zips the files and emails a link when the zip is ready rather than downloading straight away. Neither route is instant, so start it before the afternoon you need it.
Two limits in the same help centre are worth knowing before you let a form run on its own. Submission Storage is the total number of entries your account can hold, and Jotform says going past it deletes the oldest form entry to make room for the new submission. Upload Space is the account-wide disk space for files people upload through your forms, and reaching it prompts the system to disable your forms on a scheduled date, after which visitors get a Form over quota page reading that the form has exceeded its allocated quota. Freeing upload space is a two-step job in the docs: delete the entries with uploads, then purge them. That is permanent, which is the argument for exporting first.
Jotform's usage guide names both limits and prints no numbers for either. It sends you to the Features and Pricing page for the per-plan breakdown, so anybody who quotes you a figure from a blog is guessing. One number does appear in Jotform's own FAQ, read on 22 October 2026: on a downgrade your data stays stored as long as it does not go over the total submission storage on free accounts, which is 500, and your forms will be disabled if you go over the monthly submission limit on the downgraded plan or any other limit, such as the number of forms. The FAQ does not say what becomes of the entries already above that line, so treat a downgrade as a reason to export rather than a thing to try and see.
This is the half that makes a rebuild cheap. Your entries are rows in Jotform Tables with named fields, your uploads are files you can pull as a zip, and a form submission is an HTTP request that a phone can make as well as a browser. Plenty of good apps keep posting to Jotform and simply replace the screen in front of it. The same split turns up with any tool that owns the front end and not the data, which is why builder io to mobile app arrives at the same conclusion from a different starting point.
Can you put a Jotform app on the App Store?
Jotform does not document a way, so the only route left is the one people invent: build a small app whose single screen loads your app URL. You can write that in an afternoon. Apple has two sentences about it. Guideline 4.2 says your app should include features, content and UI that elevate it beyond a repackaged website, and that an app which is not particularly useful, unique or app-like does not belong on the App Store. Guideline 4.2.2 says that other than catalogs, apps should not primarily be marketing materials, advertisements, web clippings, content aggregators or a collection of links. A frame around a form link is the thing both sentences were written about.
Read what the guideline does not say, because this gets overstated. Web views are allowed, and a lot of shipped apps contain them. The test is about the app as a whole, whether there is enough of it to be worth installing. A real form screen, a list that opens in a basement with no signal, a scanner, a notification when a new entry arrives: each of those moves you toward the right side of the line, and a wrapper moves you nowhere.
There is a quieter problem with the wrapper, which is that it fails at the thing you wanted. A page loaded over the network needs the network. It holds no state when the signal drops halfway through a long submission, and it gets you no further on notifications than the home screen shortcut already does, because Apple's own documentation on web push puts that feature on Home Screen web apps in iOS 16.4 or later, read on 22 October 2026. If the shortcut already covers it, the wrapper has bought you an App Review queue and nothing else.
A shared link and an installed app, side by side
The left column is what Jotform documents today. The right column is what an installed build gives you. Read it as a list of jobs rather than a scoreboard, because for a form that forty colleagues fill in twice a month the left column wins on effort and never stops winning.
| The job | A Jotform app link | An app you build and ship |
|---|---|---|
| Opens at a URL in any browser | Yes | No |
| Embeds in a website you already have | Yes, as an embed code or a WordPress shortcode | No |
| Listed on the App Store or Google Play | No | Yes |
| Sits on the home screen | Yes, as a shortcut that opens in the browser | Yes, as an installed app |
| A change reaches everyone with no review | Yes | Only for the part you can update over the air |
| Goes through App Review | No | Yes |
| Entries land in Jotform Tables | Yes | Only while you keep Jotform in the path |
What carries over if you build it properly?
Your data and your field names, because they never move. Your notification emails and your integrations keep firing, since they hang off the submission rather than off the page that sent it. What you are rebuilding is the screen, the navigation and the login, and the login is the one people underprice. Jotform gives you three access levels, optional registration, an expiring share link and SSO on Enterprise, for the cost of a subscription. Matching that in your own app is a week of work before anybody sees a form field.
Two things are worth settling before you draw a single screen. Payments are the first, because a Jotform payment field is a web payment and a phone is a reviewed platform, so what you sell decides which of Apple's rules applies to you. File uploads are the second. A phone camera produces far bigger files than a laptop upload form, which runs you into Jotform's upload space limit faster than you expect, and that limit disables forms rather than warning you forever.
Newly is an AI app builder for this job. You describe the app in plain English and it writes a real React Native and Expo project that you own, with two-way GitHub sync so the code is never somewhere you cannot reach. It uploads iOS builds to TestFlight, publishes to Google Play internal testing and builds a standalone Android APK. It is $25 a month, with no free tier. What it will not do is press submit for you, and that is on purpose: guideline 4.2.6 says apps created from a commercialized template or app generation service are rejected unless submitted directly by the provider of the app's content, so the submission stays yours. The mechanics of that step are in publish to app store.
The honest recommendation is to do less than you came here to do. Turn on the home screen shortcut, keep the link, and give it a month. If people still ask for an app after that, make them say why. Concrete answers are worth building for: no signal in the stockroom, a camera that has to work properly, a listing customers can find, a scanner at the door. If the answer is that a link feels less serious than an app, you have a branding problem rather than an engineering one. For a starting point that is a design rather than a form, the same reasoning is in locofy to mobile app.
Questions people ask about Jotform and mobile apps
It produces a web app at a link. Jotform's help centre says that once your app is published, people can use it either by installing it on their device for quick access or by opening it directly in their web browser, and the Publish tab offers an app link, an email invitation, social sharing, a QR code and an embed code. There is no build step, no signing, no file to install and no store submission anywhere in those pages. Read on 22 October 2026 from the Jotform Apps guide.
Export the data first. Then describe the screens.
Write down your fields, the table they land in, and the one job a link cannot do for you. That list is the brief for the app, and the tables and emails behind it do not have to change at all.
Start building