Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.replit.com/llms.txt

Use this file to discover all available pages before exploring further.

An app is software designed to perform a specific task for a specific person or group. Apps can be simple or complex. A calculator, booking form, dashboard, internal tool, mobile experience, marketplace, and customer portal are all apps if they help someone do something useful.

​
Apps are code that runs on infrastructure

Every app is two things working together:
  • Code — the instructions that describe what the app does: the interface someone sees, the logic that responds to clicks and inputs, and the rules for how data moves around.
  • Infrastructure — the machines, networks, storage, and services the code runs on so other people can reach it from a browser or phone.
Writing the code is the part most people picture when they think about “building an app.” Infrastructure is everything that has to be in place for that code to actually work for users: a server to run it, a database to store information, a domain so people can find it, security to protect it, and a way to update it without breaking what already works. On Replit, you describe what you want in natural language. Agent writes the code, and Replit provides the infrastructure — hosting, databases, secrets, domains, and deployments — so you can publish a working app without setting any of it up yourself.

​
Why build an app?

You might build an app when existing tools almost work, but not quite. An app is useful when:
  • You want a custom workflow
  • You have hit the limits of a spreadsheet, form, or template
  • You need a repeatable process
  • You want to test demand for an idea
  • You want teammates, customers, or users to interact with something you control
For example, an entrepreneur might build a waitlist app to test demand. A marketer might build a campaign landing page with a form. A data analyst might build a dashboard that makes a spreadsheet easier to explore.

​
Apps solve a focused problem

Good first apps are focused. They solve one clear problem for one clear audience. Instead of starting with: 
A platform for managing my entire business.
Start with: 
A page where customers can request a catering quote and receive a confirmation message.
The smaller version is easier to build, test, publish, and improve.

​
Apps and artifacts

On Replit, an app is one kind of artifact. An artifact is a publishable output from a project. Artifacts can include:
  • Web apps
  • Mobile apps
  • Data dashboards
  • Slide decks
  • Animated videos
  • Designs
  • 3D experiences
Apps are usually interactive. They often let people submit information, view data, log in, make choices, or complete a workflow. Other artifacts, such as slide decks or animated videos, may focus more on presentation or storytelling.

​
What makes an app real?

An app starts to feel real when someone can use it outside your head. That usually means:
  • It has one clear purpose
  • Someone can complete the main action
  • You can test it in Preview
  • You can publish it to a shareable URL
  • You can improve it after feedback
The first version does not need every feature. It needs to work well enough to learn from.

​
Common misconceptions

  • “An app has to be big.” Many valuable apps are small tools for a specific job.
  • “An app has to be public.” Some apps are private tools for you, your team, or your customers.
  • “An app has to be perfect before publishing.” Publishing a focused first version helps you learn what to improve.

​
Where to go next

Vibe coding

Learn the mindset for turning app ideas into working artifacts.

Learn how Replit projects hold apps, data, and artifacts.

Learn about the publishable outputs you can create on Replit.