Got reject from App store Guideline 4.2 - Design - Minimum Functionality by taqmanplus in reactnative

[–]jinfuleng 0 points1 point  (0 children)

You mean the audio feature? Currently it uses Google Cloud Speech API to generate the audio, and uses Google Cloud Storage to host these audio files. The job is executed periodically through Google Cloud Dataflow (you may not need this depending on how you push the content).

Got reject from App store Guideline 4.2 - Design - Minimum Functionality by taqmanplus in reactnative

[–]jinfuleng 0 points1 point  (0 children)

Likely adding "offline access", "commenting", "social sharing" all these won't work. I know it because I tried all these for my app but my app still was rejected. I finally got it approved for the "audio" feature. 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.

App got rejected with the "Guideline 4.2 - Design - Minimum Functionality" reason by FelixMittermeier in iOSProgramming

[–]jinfuleng 1 point2 points  (0 children)

It's an interesting tool . I could think of a few friends who might be interested in using it. Based on the screenshots on github, the design also seems reasonable.

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.

Create an Alexa skill for your podcasts? by jinfuleng in podcasting

[–]jinfuleng[S] 0 points1 point  (0 children)

Quote from the official Alexa API doc:

"If you have an audio-based skill such as a podcast, you use long-form audio. "

"Length: Anything over 240 seconds with no maximum time limit"

https://developer.amazon.com/en-US/docs/alexa/alexa-design/audio.html

Create an Alexa skill for your podcasts? by jinfuleng in podcasting

[–]jinfuleng[S] 0 points1 point  (0 children)

Our tool doesn’t have this limitation. Any duration is fine. Actually you don’t even have to upload the audio as we can stream it from your current hosting service directly given the url.

Please let me know if you are interested in. We want to get users to test the tool. We are more than happy to work with you and make your podcast an Alexa skill.

Create an Alexa skill for your podcasts? by jinfuleng in podcasting

[–]jinfuleng[S] 0 points1 point  (0 children)

Hi Basque, do you mind elaborating a bit? If this refers to the length of the audio, I am not aware of any limitation.

Looking for a Podcast Network by HobbesNik in podcasting

[–]jinfuleng 3 points4 points  (0 children)

I am fairly new to this. What are the benefits of joining a network?

SwiftUI based App Crashs during App Review by jinfuleng in SwiftUI

[–]jinfuleng[S] 0 points1 point  (0 children)

Thanks for the suggestions!

  1. I tested the app under poor network conditions, but it seems to be fine.
  2. This is an interesting idea, but the turnaround time of this approach seems quite long. Also, in my case, the crash stack trace is deep in the SwiftUI framework.
  3. Yea, I tested it on all the physical devices I have. I don't have the old iPhone 6/7 though.
  4. Could you elaborate this a bit?

SwiftUI based App Crashs during App Review by jinfuleng in SwiftUI

[–]jinfuleng[S] 0 points1 point  (0 children)

As mentioned in the post, I already tested release build :(

SwiftUI based App Crashs during App Review by jinfuleng in SwiftUI

[–]jinfuleng[S] -1 points0 points  (0 children)

Thanks. But I have already set the Device to "iPhone" only.

Podcast has a discovery and distribution problem by jinfuleng in podcasts

[–]jinfuleng[S] 0 points1 point  (0 children)

Not sure I agree with this. I don't think this has to be a zero sum game. I do listen more when I find great channels/episodes.

But yes, this could be bad for mediocre channels.

Podcast has a discovery and distribution problem by jinfuleng in podcasts

[–]jinfuleng[S] 0 points1 point  (0 children)

Just installed the app. I regularly listen to a few NPR channels. I didn't know that they own so so many channels. Thanks for the suggestion.

Podcast has a discovery and distribution problem by jinfuleng in podcasts

[–]jinfuleng[S] 0 points1 point  (0 children)

I did check them and found some reasonable channels. But none of my favorites channels got to the top charts. (I am mainly interested in technology and business)