Guideline 2.5.2 Rejection for Educational Coding App Despite Fully Visible and Editable Source Code

Hello,

I am the developer of Kodogram, an educational programming platform that allows users to learn, inspect, edit, and execute code.

My app was rejected twice under Guideline 2.5.2 despite the fact that all executable source code is fully visible and editable by users before execution.

According to Guideline 2.5.2, educational apps may download code provided that:

  • The code is used solely for educational purposes.
  • The source code is completely viewable by the user.
  • The source code is editable by the user.

Kodogram is designed specifically for programming education. Users can learn, inspect, edit, share, fork, and test source code written in multiple programming languages, including HTML, CSS, JavaScript, Python, C, C++, C#, Java, PHP, and others.

In the application:

  • Users can view the complete source code before execution.
  • Users can edit the source code before execution.
  • Users can create forks of shared projects and modify them.
  • Users can test and learn code written in multiple programming languages.
  • Code execution occurs only after the user has reviewed and optionally modified the source code.

During the review process, Apple attached a screenshot showing only the final "Run Output" screen.

In response, I provided additional screenshots demonstrating:

  • Complete source code visibility before execution.
  • Separate source code views for HTML, CSS, and JavaScript examples.
  • The code preview/editor screen where users can review and modify code.
  • The final output screen shown only after the code has been reviewed and executed.

The attached screenshots use HTML, CSS, and JavaScript as examples, but the same workflow applies to all supported programming languages within the platform.

My question is:

Has anyone experienced a similar Guideline 2.5.2 rejection for an educational coding application where the source code was already fully visible and editable before execution?

Is there any additional requirement, documentation, or implementation detail that App Review may expect beyond demonstrating that source code is completely viewable and editable by the user prior to execution?

Any guidance or shared experiences would be greatly appreciated.

Thank you.

Thank you for your post. We recommend that you sign up for a session with App Review during the weekly Meet with Apple event. Sign in with your Developer ID and select "Request a one-on-one App Review consultation". A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines.

Guideline 2.5.2 Rejection for Educational Coding App Despite Fully Visible and Editable Source Code
 
 
Q