feat(autostart): add prefered name configuration for auto start entry

[Tunglies]

Add Prefered Name Configuration for AutoStart Entry

This PR introduces the ability to customize the application name used in auto start entries by adding a PreferedName enum to support different naming strategies.

Key Changes:

• Added PreferedName enum with variants:
  • PackageInfoName (default) – Uses name from Tauri's package info
  • PackageInfoCrateName – Uses the crate name from Cargo.toml
  • ConfigIdentifier – Uses the identifier from Tauri's runtime config
  • ConfigProductName Uses the product_name from Tauri's runtime config
  • Custom(String) – Allows specifying a custom name
• Implemented Default trait for PreferedName (defaults to PackageInfoName)
• Added prefered_name builder method with documentation and usage examples
• Integrated prefered name selection into auto start configuration

Usage Example:

Builder::new()
     .prefered_name(PreferedName::PackageInfoName)
     .build();

Builder::new()
    .prefered_name(PreferedName::Custom("My Custom Name".into()))
     .build();

This enhancement provides flexibility for apps that need to control their display name in system auto start entries, supporting use cases like branding adjustments or multi-instance differentiation.

[github-actions]

Package Changes Through c5b28c0

There are 2 changes which include autostart with minor, autostart-js with minor

Planned Package Versions

The following package releases are the planned based on the context of changes in this pull request.

package	current	next
autostart	2.3.0	2.4.0
autostart-js	2.3.0	2.4.0

Add another change file through the GitHub UI by following this link.

---

Read about change files or the docs at github.com/jbolda/covector

[Tunglies]

Thanks @Legend-Master for review.

I kept the original init api which not brings a breaking change.

pub fn init<R: Runtime>(
    #[allow(unused)] macos_launcher: MacosLauncher,
    args: Option<Vec<&'static str>>,
)

To setup a app name with builder method

fn main() {
    tauri::Builder::default()
        .setup(|app| {
            app.app_handle().plugin(
                tauri_plugin_autostart::Builder::new()
                    .app_name(PreferedName::CrateName)
                    // .app_name("MyTauriAPP")
                    .build(),
            )?;

            Ok(())
        })
        .run(tauri::generate_context!())
        .expect("error while running tauri application");
}

It supports 5 naming variants: default (AppName) (package.json), CrateName (Cargo.toml), Identifier and ProductName (Tauri config), and a customizable String override.

#[derive(Default)]
pub enum PreferedName {
   #[default]
   AppName,
   CrateName,
   Identifier,
   ProductName,
   Custom(String),
}

The extra variants improve configuration file synchronization, which is a useful feature.

[Legend-Master]

The extra variants improve configuration file synchronization, which is a useful feature.

I can see it's more ergonomic to use when you need them, but I can't see when would you want to use them to be honest, for the crate name, you can just do .app_name(env!("CARGO_CRATE_NAME")), for the id, normally we should use a display name instead of a code name, and for the product name, isn't it just the app name but fallback to TauriAPP?

[Tunglies]

The extra variants improve configuration file synchronization, which is a useful feature.

I can see it's more ergonomic to use when you need them, but I can't see when would you want to use them to be honest, for the crate name, you can just do .app_name(env!("CARGO_CRATE_NAME")), for the id, normally we should use a display name instead of a code name, and for the product name, isn't it just the app name but fallback to TauriAPP?

The PreferedName::CrateName variant is redundant since it can be directly achieved via .app_name(env!("CARGO_CRATE_NAME")), making it removable.

On MacOS, the plist file path is generated based on app_name, resulting in /Users/user/Library/LaunchAgents/{app_name}.plist .
https://github.com/zzzgydi/auto-launch/blob/fedaeba7a5ee6a5124b056907e03c399acd6df27/src/macos.rs#L179-L181

and for LaunchAgent, the Label field typically uses the app's identifier for unique identification. Applications control their LaunchAgent naming through the CFBundleIdentifier specified in Info.plist .
https://github.com/zzzgydi/auto-launch/blob/fedaeba7a5ee6a5124b056907e03c399acd6df27/src/macos.rs#L95-L111

The Config structure is defines product_name: Option<String> so I added fallback just in case.
https://github.com/tauri-apps/tauri/blob/dbcfaa18d7a0a4b41fbdde5c16616cce1b702ac6/crates/tauri-utils/src/config.rs#L2941-L2948

---

#[derive(Default)]
pub enum PreferedName {
   #[default]
   AppName,
   Identifier,
   Custom(String),
}

Keep only these three variants: default to AppName (package.json), a variant using Identifier(Tauri config, particularly useful for macOS), and a Custom option allowing users to define their own logic.

Alternatively, remove the Identifier variant if you think it’s too cumbersome to handle.
So there would be just None or String, None is default to AppName or setting by String .app_name(String)

[FabianLars]

The thing here is that devs themselves can use app.config().identifier as well. It's not like we don't want them to not have a way to use the identifier without hardcoding it, it's just that the code logic of the enum can be used in their code just as well.
Imo that's good enough to keep our api small and simple 🤷

[Tunglies]

Thanks @Legend-Master and @FabianLars for reviews.

Let's keep the api small and simple.

The only one additional function for builder is

/// Sets the app name to be used for the auto start entry.
///
/// ## Examples
///
/// ```no_run
/// Builder::new()
///     .app_name("My Custom Name"))
///     .build();
/// ```
pub fn app_name(mut self, app_name: &str) -> Self {
    self.app_name = Some(app_name.to_string());
    self
}

no more, no less.

[FabianLars]

Thank you! And sorry for being kinda harsh about your ideas. In theory I like them but with the very limited resources we have for maintenance I try to keep things simple like that.

[Legend-Master]

Generally looks good, just a few nit picks, thanks for the contribution

Also could you add a change file?

https://github.com/tauri-apps/plugins-workspace/blob/v2/.changes/readme.md

[Tunglies]

Generally looks good, just a few nit picks, thanks for the contribution

Also could you add a change file?

https://github.com/tauri-apps/plugins-workspace/blob/v2/.changes/readme.md

I added the change file. Let's go

[Legend-Master]

Thanks!