Zap Studio

Project Identity

How to update your app's name, version, and branding after cloning Local.ts.

After cloning Local.ts, you'll want to update several files to match your project's name, description, and branding.

Files to Update

FileFields to Update
package.jsonname, version, description
index.htmltitle
src/constants/index.tsAPP_TITLE
src-tauri/Cargo.tomlname, version, description, authors
src-tauri/tauri.conf.jsonproductName, version, identifier
splash.htmlApp name and description text

Step-by-Step Guide

1. Update package.json

{
  "name": "my-awesome-app",
  "version": "1.0.0",
  "description": "A brief description of your app"
}

2. Update index.html

<title>My Awesome App</title>

3. Update App Constants

In src/constants/index.ts:

export const APP_TITLE = "My Awesome App";

This constant is used throughout the frontend for window titles and UI elements.

4. Update Cargo.toml

In src-tauri/Cargo.toml:

[package]
name = "my-awesome-app"
version = "1.0.0"
description = "A brief description of your app"
authors = ["Your Name <you@example.com>"]

5. Update Tauri Configuration

In src-tauri/tauri.conf.json:

{
  "productName": "My Awesome App",
  "version": "1.0.0",
  "identifier": "com.yourcompany.myawesomeapp"
}

The identifier should be a unique reverse-domain identifier for your app. This is used for:

  • macOS bundle identifier
  • Windows application ID
  • Linux desktop file

6. Update Splash Screen

In splash.html, update the visible text:

<h1>My Awesome App</h1>
<p>Loading your awesome experience...</p>

Bundle Identifier

The bundle identifier in tauri.conf.json is important for:

PlatformUsage
macOSBundle ID, code signing, App Store
WindowsApplication User Model ID
LinuxDesktop entry file name

Choose a unique identifier following reverse-domain notation. Here are some examples:

  • com.yourcompany.appname — For company apps
  • dev.yourname.appname — For personal projects
  • io.github.username.appname — For open source projects

Version Management

Keep versions synchronized across all configuration files. When releasing a new version, update:

  1. package.json
  2. src-tauri/Cargo.toml
  3. src-tauri/tauri.conf.json

Consider using a tool like changesets to manage versioning across the monorepo.

Edit on GitHub

Last updated on

On this page