# Advanced Prompting For App Creation

## How to Think Through Your App Idea Before Building with eMOBIQ AI

When building an app using **eMOBIQ AI**, it's not just about filling out forms or ticking boxes — it's about telling a story. A story about a problem someone has, how your app will solve it, and what success looks like when it all works together.

This guide helps you **think like a builder** , guiding you through a structured yet flexible process that starts with real-life scenarios and ends with a clear blueprint for your next application.

***

### Start With the Why: What Problem Are You Solving?

Every great app begins with empathy — understanding who your user is and what they struggle with. This isn’t just theory; it’s practical thinking that shapes every decision you’ll make while developing your app and debugging it with [Debug Agent ](/emobiq-ai/readme/debug-agent.md)to meet your app needs.

#### Example Use Case:

**Meet Sarah**\
Sarah is a therapist who journals daily to manage her mental health and reflect on client sessions. She’s tried digital apps before, but none feel personal enough or give her a visual way to track how she’s feeling over time.

She wants something simple, calming, and reflective — a space where she can write, tag her mood, and look back on how she’s doing week to week.

{% hint style="success" %}
*Tip: Try writing a short paragraph like this one about your ideal user. It doesn't have to be long — just enough to ground your thinking in a real person with a real need.*
{% endhint %}

{% stepper %}
{% step %}
**Step 1: Define the Core Purpose of Your App**

Now that you’ve got a user in mind, ask yourself:

* What does your app help people **do** ?
* What kind of **problems** does it solve?
* Why would someone **choose this app** over another tool?

**Prompt:**

> “I’m building an app that helps \[type of person] do \[key action] by \[how it makes it easier/faster/better].”

**Example:**

> “I’m building an app that helps individuals track their thoughts and moods daily by offering a calm, intuitive interface where entries are tied to a calendar and tagged with emotions.”
> {% endstep %}

{% step %}
**Step 2: Identify the Must-Have Features**

These are the features that define your app — the ones that make it *yours* and ensure it solves the problem effectively.

Ask yourself:

* What should your app **do without fail** ?
* What are the **essential interactions** your users will perform?
* What happens if those things aren’t there?

{% code title="Example Prompts:" %}

```
Allow users to create, save, and edit daily diary entries.
Tag each entry with a mood (happy, anxious, tired, etc.).
Display entries on a calendar view with color-coded mood indicators.
Enable filtering and searching by date, keyword, or mood.
```

{% endcode %}

Then add a few **nice-to-have features** that enhance the experience:

* Daily prompts or templates for users who need inspiration.
* Reminders to encourage consistent journaling.
  {% endstep %}

{% step %}
**Step 3: Envision the Look and Feel**

Your app’s design plays a big role in how users engage with it. Even the most powerful tools can fall flat if they don’t feel good to use.

Think about:

* What kind of **vibe** should your app give off? (Calm? Energetic? Minimal?)
* How should users **feel** when they open it?
* Do certain colors or layouts already come to mind?

{% code title="Example Prompts:" %}

```
Clean, minimal, and emotionally soothing.
Mood tags displayed clearly on a calendar.
Pastel tones and soft visuals to promote reflection.
Light/dark mode toggle for personal preference.
```

{% endcode %}
{% endstep %}

{% step %}
**Step 4: Consider Special Requirements or Limitations**

Some ideas are best left out — either because they complicate things unnecessarily or because they distract from the core purpose.

Also consider extras that might be optional now but useful later.

{% code title="Example Prompts:" %}

```
Export entries to PDF or plain text for offline sharing.
Add a gratitude log section or customizable tags.
Don’t include analytics or dashboards — keep the focus on journaling, not performance tracking.
```

{% endcode %}
{% endstep %}
{% endstepper %}

### Why This Matters for eMOBIQ AI

Because eMOBIQ AI allows deep integration with APIs, databases, and logic execution, having a strong conceptual foundation ensures:

* Smooth setup of API connections and authentication
* Clear mapping of frontend components to backend logic
* Reliable testing and iteration using built-in tools
* Better alignment between your vision and the AI-generated solution

It also gives the system more context to work with — so when you say "build me a diary app", eMOBIQ AI understands not just what you’re asking for, but **why** you’re asking for it.

***

### Final Thoughts

The goal of this guide isn’t to box you into a template — it’s to help you **tell a story** about your app idea in a way that’s both **clear and compelling**.

Whether you're building a diary app, invoice processor, or team collaboration tool, starting with the human behind the problem will always lead to better outcomes.

So go ahead — write the story of your app. eMOBIQ AI will take care of the rest!


---

# 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.emobiq.com/emobiq-ai/readme/building-your-app/advanced-prompting-for-app-creation.md?ask=<question>
```

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.