Build flavor difference

Root cause

There are some reasons that some of the SDAI app features can not be distributed through different sources because of rules and compliance policies.

Build flavors

To avoid compliance/licensing issues there are three app flavors (types):

• playstore:
  • distributed through Google Play and GitHub releases;
  • does not contain features that does not comply with Google Play rules/policies.
• foss:
  • distributed through F-Droid and GitHub releases;
  • contains only FOSS dependencies;
  • best choice for users that care about FOSS philosophy and privacy.
• full:
  • distributes through GitHub releases;
  • contains ALL available features, best choice for users that want to have every app feature without caring about

Difference between flavors

#	Feature	playstore	foss	full	Details
1	Sideloading LocalDiffusion (ONNX and Google MediaPipe) custom model	❌	✅	✅	Google Play does not allow publishing apps with android.permission.MANAGE_EXTERNAL_STORAGE permission, which is required to read custom model files from external storage directly.
2	LocalDiffusion Google AI MediaPipe generation provider	✅	❌	✅	This generation provider is build with library com.google.mediapipe:tasks-vision-image-generator that includes user tracking Google Firebase libraries and telemetry without mentioning about it anywhere in their documentation. Unlike Google, SDAI app respects your freedom and privacy, so this generation provider will never be included in foss build.
3	Reporting inappropriate image content to SDAI-reporting server	✅	❌	✅	Google Play require that AI apps should contain in-app user reporting or flagging features that allow users to report or flag offensive content (for the details see Google Play AI content policy. Feature introduced since 0.6.5, removed from FOSS build since 0.6.7