Apps FAQs

Answers to common questions about building Kissflow Apps, trying them out, the App Store, and public access to apps.

What programming languages can I use to create Kissflow Apps?

Kissflow Apps isn't tied to a single programming language. Our Software Development Kit (SDK) is designed for client-side apps and is written in JavaScript. To interact with server-side apps, use the Run script connector in Integration.

Can I get a Kissflow Apps account for testing purposes?

Yes. If you don't already have an account, sign up for a free trial with your work email address at Kissflow. Trial availability and duration depend on your plan, so check the current pricing page for details before you sign up.

Is there a central platform to access different low-code apps?

Yes — the Kissflow App Store. It hosts ready-made apps you can install with little to no coding, and you can also build and share your own apps with other Kissflow users. See Introduction to Kissflow App Store to get started.

How do I provide public access to an app?

Kissflow Apps themselves don't support public links, so there's no direct way to make an entire app publicly accessible. Specific components within an app, such as processes, offer limited public access through public forms. These let external users interact with a process form without accessing the app itself.

Since apps can't have public links, share access intentionally instead: invite the users you want to have access and assign them appropriate roles. They need to be licensed users to open the app.

If you need to collect data from external users, use a public link on the specific process that needs it rather than trying to share the whole app. Public process links are built for external interactions like form submissions, while the app itself stays private.

What if I need an entire app to be public?

Use a Kissflow Portal instead. Portals are built for sharing flows and apps with external users who don't have a Kissflow license.