> For the complete documentation index, see [llms.txt](https://se4ma.gitbook.io/book/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://se4ma.gitbook.io/book/chapter3.md). # Chapter 3: Give me a context and I will give you an app \#Chapter 3: Give me a context and I will give you an app (By Mario Linares-Vásquez and Sergio Velásquez) *** One of the powerful elements in design thinking is the empathize step, and in particular, the philosophy of understanding the problems and situations from an "inside-out" perspective. In that sense, understanding the context is a "must" if we want to apply design thinking in a mobile app development process. But what is a context? The merriam-webster dictionary defines context as *"the interrelated conditions in which something exists or occurs : environment, setting"* Pretty easy definition, right? But, in the **context** of a mobile app, what is the **context**? Well, the context is everything that surrounds the app, the environment where the app will be installed and used. A solution that does not consider the context is a solution (i) expected to fail with a high probability, or (ii) expected to work only on the "happy paths". For example, assume there is a device with a display panel in which the contrast/brightness can not be modified, by default it is in a low-energy mode, and the display is located in such a way that during sunny days, the light goes directly to the display. What is the problem? You can not operate the display because you do not see anything on it !!! (This is a real problem in some of the copy machines in the university) What was the problem? The display in the copy machines was designed without considering the context, and in particular, different settings/environments in which the machine could be operated. Now , lets say you are going to design a solution for personas with disabilities. You need to be in their shoes to design a good solution, you need to understand the context. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://se4ma.gitbook.io/book/chapter3.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.