--- title: "Intro: Apps and solutions" slug: "intro-apps-and-solutions" tags: ["App Builder", "App Building", "Get started"] updated: 2025-05-13T17:56:06Z published: 2025-05-13T17:56:06Z canonical: "support.tulip.co/intro-apps-and-solutions" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.tulip.co/llms.txt > Use this file to discover all available pages before exploring further. # Intro: Apps and solutions **In this guide, you will learn:** - **Three basic elements of an app** - **How an app fits into a solution** - **What makes a solution impactful for your operation** - **Essential principles each solution needs** ## Apps A Tulip app is a piece of software geared towards helping an end user complete tasks that resemble their physical workflow. An app should perform discrete tasks and address a specific business problem in a specific location or physical environment. The core value of Tulip apps is to replicate your physical operations. These apps could be: - Guided workflows that walk operators through steps to complete tasks, like work instructions. - Dashboards that compile real-time production data - Inventory terminal with kanban capabilities for replenishment - Rework management that routes rework to operators and notifies quality control ![Rework Parts Status Step Ex](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Rework%20Parts%20Status%20Step%20Ex.png) Apps are as customizable as you need them to be. There are three elements that make up an app: ### Design The layout, organization, physical appearance, and color scheme of steps and the components on a step. Design also includes naming conventions for components. ![Color%2011](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Color%201%281%29.jpg) Learn more about app design [here](/r230/docs/app-design-best-practices). ### Functionality How the app logic performs, such as: trigger behavior, step navigation, or widget configuration ![WI One Task per Step](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/WI%20One%20Task%20per%20Step.gif) Learn about how to build app functionality in the Tulip University Basic App Design and Logic course [here](https://university.tulip.co/basic-app-design-and-logic). ### Architecture The defined scope of the app, the data that’s read from or written to, and the integrations and/or devices connected. Below is an example of a basic app architecture diagram: ![App architecture diagram ex.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/App%20architecture%20diagram%20ex.png) Learn about app architecture through our interactive diagram [here](https://architecture.tulip.co/). ## Solutions A Tulip solution is collection of artifacts (apps, data model, physical devices) and functionalities (routing, automations, monitoring, integrations). Think of it as a system that connects apps, what they need to run, and all the digital parts (i.e. like data from tables, connections to other systems, and physical devices). The image below shows a typical map of physical stations to apps that work together and form a solution: ![App Solution to Physical Mapping](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/App%20Solution%20to%20Physical%20Mapping.png) ### What does a solution do? Solutions are built to satisfy business objectives and continually solve operational problems. They are designed to **evolve and grow alongside your operations**, as Tulip apps are continuously improved based on real-world feedback, performance analysis, and functionality requirements. **A solution must take a human-centric approach**, which means consider the human element in the work that operators do and how they do it, including tools, devices, and equipment. #### Example A human-centric design takes into account if operators are wearing gloves, and therefore unable to use touch screens, by using devices like barcode scanners, foot petals, digital weighing and measuring devices, or wearables, like Proglove. ### How do I make sure a solution solves the right problem? It is easy to get into Tulip and build an app that solves a problem, but you will see the most value by focusing on business objectives in order to identify key problems. Then you can **build a solution around what provides the most value**. A successful Tulip solution involves the following key steps: 1. **Define Business Objectives:** Clearly establish business objectives and align the project's scope with these objectives. 2. **Document Physical Operations:** Thoroughly understand and document the physical operations within the scope of the project. This includes mapping how, where, and when frontline operators will interact with the solution. 3. **Document Operator Activities and Processes:** Gain a comprehensive understanding of the operator activities and processes the solution will support. 4. **Develop Iterative Wireframes:** Create wireframes representing operator tasks and workflows. These wireframes will evolve throughout the iterative solution building process, ultimately becoming the actual solution. The image illustrates this process: ![Multi perspective solution design](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Multi%20perspective%20solution%20design.png) Learn more about how to design a Tulip solution [here](/r230/docs/how-to-design-a-tulip-solution). ### Core necessities of a solution The following principles are essential for a scalable, human-approachable solution: - **Solutions are broken into apps** by considering the smallest logical blocks–solution components–that make sense for a given Shop Floor. A solution might be broken into separate apps based on place, time, and role. Apps should have a 1:1 app to workflow ratio: what activities is this operator performing at this location during this specific time? This model is known as Composability. Learn more about building composable apps [here](https://support.tulip.co/docs/how-to-build-composable-apps). - **Solutions and their components should be able to pass a “hit-by-a-truck” test**, meaning one process engineer should be able to understand and support the solution if another process engineer in the same area developed it. - **Solutions follow a flexible and composable common data model**, like the Tulip Common Data Model. Learn more about common data modeling in Tulip [here](/r230/docs/how-to-use-a-common-data-model). - **Solutions follow defined best practices**, such as those outlined in the [Tulip Solution Credo](/r230/docs/tulip-solution-credo). These best practices ensure alignment across every digitally represented process. **Solution components are standardized and templated whenever possible**. For example, a component library containing step templates that include base layouts, checklists, forms, and so on. ## Next Steps Start building apps with Tulip experts’ guidance: - [Walkthrough: Build your first app](/r230/docs/walkthrough-build-your-first-app) - [App building basics](/r230/docs/app-building-basics) - [Basic App Design and Logic University Course](https://university.tulip.co/basic-app-design-and-logic) --- Did you find what you were looking for? You can also head to [community.tulip.co](https://community.tulip.co/?utm_source=intercom&utm_medium=article-link&utm_campaign=all) to post your question or see if others have faced a similar question! **Composability** **Composability**in software is the concept that resources, logic, and assets can be reused throughout solutions. When this comes to Tulip, Compostability matters when developing apps and data architecture that can be used by multiple teams, facilities, and roles.