Merge pull request #73 from flathub/id-verification

flathub-infra · Aug 25, 2023 · 7f633e1 · 7f633e1
2 parents 591456c + 5b5161a
commit 7f633e1
Showing 1 changed file with 2 additions and 0 deletions.
diff --git a/docs/02-for-app-authors/02-requirements.md b/docs/02-for-app-authors/02-requirements.md
@@ -17,6 +17,8 @@ using the `extra-data` source type.
 
 Each application should have a unique application ID, following the standard reverse-DNS schema. See [the Flatpak documentation](http://docs.flatpak.org/en/latest/conventions.html#application-ids) for more information on this. The Application ID should be a real URL of a domain that the app author has control over or where their app is hosted.
 
+Ignoring this will lead to problems down the line, such as not being able to verify the app and receiving payments. It also decides, which verification methods will be available. For e.g. using `io.github.flathub.TestApp` would only allow for `Github` or `Website` verification.
+
 ## Repository layout
 
 The manifest must be at the top level and named after the application ID with the extension