I recently launched a news app. It's hard. My app was also rejected many times for the same reason. Below I am going to paste my answer from another similar thread. Hope it helps. I recently finally launched my app to the App Store. It was consistently rejected for the same reason (Guideline 4.2.2 - Design - Minimum Functionality) for about a month before the first approval. It was a very struggling experience. Below are the things I tried. I hope it could help people who are in a similar situation. Context: My app is for reading tech news (e.g. TechCrunch) and Venture Capital blogs (e.g. YC, A16z). I also use ML to generate audio for articles so users can listen to them like a podcast. More details: https://apps.apple.com/us/app/id1529509067 Here are the things I tried: Explain to reviewers that by nature a news aggregation app will mainly include links. Failed. Show thumbnails for articles. Failed.  Load parsed content directly instead of showing the source websites. Failed Add the "article bookmark" feature. Failed. Explain to reviewers that "article bookmark" uses persistent storage and it can't be done through a website. Failed. Add the "article commenting" feature. Failed. Update the app metadata (e.g. description, screenshots) to highlight the "audio" feature. Failed. Explain to reviewers that "audio" is a differentiator and the feature largely leverages native iOS functionalities. Approved! Looking back, in my case, the original concept of "listen to articles" was probably already sufficient, but we just really need to help reviewers get it.

I recently finally launched my app to the App Store. It was consistently rejected for the same reason (Guideline 4.2.2 - Design - Minimum Functionality) for about a month before the first approval. It was a very struggling experience. Below are the things I tried. I hope it could help people who are in a similar situation. Context: My app is for reading tech news (e.g. TechCrunch) and Venture Capital blogs (e.g. YC, A16z). I also use ML to generate audio for articles so users can listen to them like a podcast. More details: https://apps.apple.com/us/app/id1529509067 Here are the things I tried: Explain to reviewers that by nature a news aggregation app will mainly include links. Failed. Show thumbnails for articles. Failed.  Load parsed content directly instead of showing the source websites. Failed Add the "article bookmark" feature. Failed. Explain to reviewers that "article bookmark" uses persistent storage and it can't be done through a website. Failed. Add the "article commenting" feature. Failed. Update the app metadata (description, screenshots) to highlight the "audio" feature. Failed. Explain to reviewers that "audio" is a differentiator and the feature largely leverages native iOS functionalities. Approved! Looking back, in my case, the original concept of "listen to articles" was probably already sufficient, but we just really need to help reviewers get it.

I recently finally launched my app to the App Store. It was consistently rejected for the same reason (Guideline 4.2.2 - Design - Minimum Functionality) for about a month before the first approval. It was a very struggling experience. Below are the things I tried. I hope it could help people who are in a similar situation. Context: My app is for reading tech news (e.g. TechCrunch) and Venture Capital blogs (e.g. YC, A16z). I also use ML to generate audio for articles so users can listen to them like a podcast. More details: https://apps.apple.com/us/app/id1529509067 Here are the things I tried: Explain to reviewers that by nature a news aggregation app will mainly include links. Failed. Show thumbnails for articles. Failed.  Load parsed content directly instead of showing the source websites. Failed Add the "article bookmark" feature. Failed. Explain to reviewers that "article bookmark" uses persistent storage and it can't be done through a website. Failed. Add the "article commenting" feature. Failed. Update the app metadata (description, screenshots) to highlight the "audio" feature. Failed. Explain to reviewers that "audio" is a differentiator and the feature largely leverages native iOS functionalities. Approved! Looking back, in my case, the original concept of "listen to articles" was probably already sufficient, but we just really need to help reviewers get it.

I recently finally launched my app to the App Store. Before that, my app was consistently rejected for the same reason (Guideline 4.2.2 - Design - Minimum Functionality). In total, it took about a month from the first submission to the first approval. It was a very struggling experience. Below are the things I tried. I hope it could help people who are in a similar situation. Context: My app is for reading tech news (e.g. TechCrunch) and Venture Capital blogs (e.g. YC, A16z). I also use ML to generate audio for articles so users can listen to them like a podcast. More details: https://apps.apple.com/us/app/id1529509067 Here are the things I tried: Explain to reviewers that by nature a news aggregation app will mainly include links. Failed. Show thumbnails for articles. Failed.  Load parsed content directly instead of showing the source websites. Failed Add the "article bookmark" feature. Failed. Explain to reviewers that "article bookmark" uses persistent storage and it can't be done through a website. Failed. Add the "article commenting" feature. Failed. Update the app metadata (description, screenshots) to highlight the "audio" feature. Failed. Explain to reviewers that "audio" is a differentiator and the feature largely leverages native iOS functionalities. Approved! Looking back, the original concept of "listen to articles" was probably already sufficient, but we just really need to help the reviewers get it.

Just checked, the Xcode is "Version 11.5 (11E608c)"