# Use Cases By use case * **Full stack mobile app:** A company uses Hatch Apps to build a mobile app and API. * **Stand alone mobile app**: A company uses Hatch Apps to build a mobile app connected to an existing API. * **Stand alone API**: A company uses Hatch Apps to build an API connected to other parts of their existing stack. * **API connected to another no-code product**: A company uses Hatch Apps to build an API that is connected to an app built with Adalo, Glide, Unqork, or another service. * **Pass through API**: A company uses Hatch Apps to build an API that aggregates data from multiple sources into a single endpoint. * **Stand alone Database**: A company uses Hatch Apps to build a SQL database * **Workflow Automation**: A company uses Hatch Apps to build a mobile app, API, and / or database that is integrated with other apps to automate a specific workflow. * **Business Process Management**: A company uses Hatch Apps to automate a business process by connecting a mobile app, API, and database to other apps. * **Robotic Process Automation**: A company uses Hatch Apps to automate a business process with smart decisioning and logic by connecting a mobile app, API, and database to other apps. * **Case Management**: A company uses Hatch Apps to manage a mobile workflow with customers or employees on-the-go. * **Mobile Data Capture**: A company uses Hatch Apps to build a mobile app and API to capture data available to mobile devices. This includes text, photos, videos, GPS location, and more. * **Prototyping**: A company uses Hatch Apps to prototype and validate a new idea before investing in software development. By persona * **Entrepreneur**: An entrepreneur uses Hatch Apps to build a mobile app and API to launch a new idea. * **Association**: An association uses Hatch Apps to build a mobile app for their members to improve renewal rates, build community, and send announcements. The mobile app is connected to their AMS for authentication, payments, members list, and more. * **Enterprise**: An enterprise uses Hatch Apps to build a mobile app connected to an existing API. This can be to manage users, payments, notifications, data, and more. * **Agency**: An agency uses Hatch Apps to build mobile apps and APIs for their clients. * **Freelancer**: A freelancer uses Hatch Apps to build mobile apps and APIs for their clinets. * **Non profit**: A non profit uses Hatch Apps to build a mobile app to convey their mission, build a community, and engage donors. By role * **Designers**: A designer uses Hatch Apps to design and build at the same time. No more handoffs to the engineering team or waiting for feedback. Drag-and-drop components and customize them with the rest of the design team. Like Figma for software. * **Engineers**: An engineer uses Hatch Apps to build and manage an API. Configure permissions, objects, rule, and routing instantly. Test your data and build custom workflows in-browser. * **Business**: A business user uses Hatch Apps to build software without coding. No more waiting for design or engineering. Drag-and-drop components and customize them as fast as you can think. If you need help, purchase a vendor on the Marketplace. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.hatchapps.com/use-cases.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.