Post #1055355

Maybe I missed something, lets look at the flatpak docs again (which aren't as formal as the other ones): https://docs.flatpak.org/en/latest/conventions.htmlAs will be seen below and in future sections, this ID is expected to be used in a number of places. Developers must follow the standard D-Bus naming conventions for bus names when creating their own IDs. This format is already recommended by the Desktop File specification and also the Appstream specification.Yes, cool, flatpaks must follow the dbus bus name conventions. They should also match desktop file names and appstream names.while not required, the application portion is recommended to be in lowercase as welland they should be all lowercase ​:neobot_explode:​ Lets look at examples. That should help. The freedesktop spec was made in large parts by GNOME and KDE, lets check out what they do. This will solve the ambiguity. KDE KColorChooser flatpak manifest "id": "org.kde.kcolorchooser", and this matches their desktop file, org.kde.kcolorchooser.desktop now, GNOME SystemMonitor flatpak manifest "app-id": "org.gnome.SystemMonitor.Devel", this matches their desktop file, org.gnome.SystemMonitor.desktop nice. cool. thank you. glad we're consistent ​:neobot_explode:​