# Minimum functionality rejection

### How do you handle iOS app rejections due to minimum functionality? 

Apple may reject your app if it does not meet the minimum functionality requirement. If you’ve received a message stating:

*“We found that the usefulness of your app is limited by the minimal amount of content or features it includes."*

It means Apple considers your app too basic or too similar to a repackaged website. Here’s what you can do to improve your app and get it approved:

#### 1. Ensure your app is **complete before submission**

* Make sure all content, button texts, links, and media are in place.
* Remove placeholder text and conduct thorough testing.
* Submit a fully functional version of your app.

{% hint style="warning" %}
Submitting an unfinished app significantly increases the chances of rejection.
{% endhint %}

#### 2. Incorporate **strong native functionalities**

Apple expects apps to behave like native applications, not just web-based experiences. Here are some ways to achieve this:

* Hide unnecessary web elements – Remove website headers and footers from your web view to prevent your app from looking like a mobile website.
* Use a native menu – Create an intuitive navigation menu to improve the app experience.
* Enhance navigation – Implement features like Bottom Navigation Bar, In-app Chat, Push Notifications, and Monetization to improve user engagement.

{% hint style="warning" %}
Apps should offer a seamless mobile experience, not just display web pages in an app shell.
{% endhint %}

#### 3. Make your app **"app-like"**

Apple wants apps to have lasting value and interactivity. If your app functions more like a catalog, webpage, or simple video gallery, it may not be approved.

* Include interactive features like search, forms, bookmarking, or in-app purchases.
* Ensure smooth navigation with native animations and transitions.
* Avoid submitting an app that just displays a few static pages or images.

{% hint style="warning" %}
If an app doesn’t provide users with new functionality beyond what a website can, it may not be considered a valid app.
{% endhint %}

#### 4. Strengthen your **app concept**

Apple prioritizes quality, trust, and a great user experience. Your app should offer something unique or useful.

* Ensure the app’s core purpose is NOT just marketing—avoid excessive promotional material.
* Match your app description and metadata with the actual functionality of the app.
* Avoid empty pages—every section of the app should have valuable content.

{% hint style="warning" %}
Your app should solve a problem, enhance convenience, or provide entertainment in a way that a simple website cannot.
{% endhint %}

#### 5. Engage users with **interactive features**

Apple favors apps that encourage user interaction. Here’s how you can achieve that:

* Add chat, comment sections, ratings & reviews, or discussion forums.
* If additional downloads are required (e.g., resource-heavy apps), disclose this upfront.
* Keep the user journey intuitive—make navigation, onboarding, and interactions seamless.

#### Final Thoughts

If your app was rejected due to minimum functionality, revisit its features, usability, and overall value. 

{% hint style="success" %}
Ask yourself:

* Does my app offer a unique function or user experience?
* Is there enough content and interactivity to keep users engaged?
* Does my app feel complete and polished?
  {% endhint %}


---

# 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.appmysite.com/frequently-asked-questions/publishing-and-distribution/minimum-functionality-rejection.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.