@### Issue Details

Hello Matt,

I'm John from Nigeria - we've been emailing. Here are my suggestions for improving the Windows experience:

Issue 1: Executable Naming

Current: timelinize.exe (lowercase 't')
Suggested: Timelinize.exe (capital 'T')

Reason: Most Windows applications use capital letters for executable names. This would make it look more professional and consistent with Windows conventions.

Issue 2: Default Icon

Current: Generic blue-and-white Windows placeholder icon (shows as "unknown publisher")
Issue: Makes the app look unfinished or corrupted to Windows users

What I did: I manually snipped the Timelinize logo from the GitHub repo, cropped it, converted to .ico format, and applied it to the executable.

Suggestion: Include a proper .ico file with the Windows build and code-sign the executable to avoid the "unknown publisher" warning.

Issue 3: Windows Installation Documentation Needs More Detail

Current problem: The Windows installation steps are too brief for non-technical users. It took me significant trial and error—I initially downloaded the wrong vips architecture, forgot to properly add libvips to my PATH (even thought I needed GTK at first!), but eventually got it running after 2-4 hours of troubleshooting at 2-4 AM.

While I'm comfortable with following docs and setting environment paths, many Windows users who just want to install the app would struggle with the current instructions.

Current instructions are:

1. Install vips:
   1. Go to the latest vips release for Windows.
   2. Download the asset for your platform architecture with -all- in the name.
   3. Extract the archive, or at least the `bin` subfolder, to a path of your choosing.
   4. Add the full path of the extracted `bin` folder to your `Path` environment variable.
   5. Restart any open shells/command prompts.
2. To process photos/videos from iPhones, install libheif
3. Install ffmpeg: curl.exe https://webi.ms/ffmpeg | powershell
4. Install uv: powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
5. Download Timelinize
6. Extract the program, timelinize.exe
7. Run the program (override Windows security warnings)

Suggested improvements:

More Detailed Step 1 (vips installation):

1. Install vips:
   a. Go to https://github.com/libvips/libvips/releases
   b. Scroll to "Assets" section
   c. **For 64-bit Windows (most common):** Download `vips-dev-w64-all-8.x.x.zip`
   d. **For 32-bit Windows (rare):** Download `vips-dev-w32-all-8.x.x.zip`
   e. **How to check your system:** Press ⊞ Win key → type "About" → check "System type"
   f. Extract the downloaded .zip file to `C:\vips` (or your preferred location)
   g. **Add to PATH:**
      - Press ⊞ Win key → type "environment variables" → click "Edit the system environment variables"
      - Click "Environment Variables" button
      - Under "System variables", find "Path" → click "Edit"
      - Click "New" → paste the full path to the `bin` folder (e.g., `C:\vips\vips-dev-8.x\bin`)
      - Click OK on all windows
   h. **Verify installation:**
      - Open a NEW Command Prompt (Win+R → type `cmd` → Enter)
      - Type: `echo %Path%` and verify your vips path appears
      - Type: `vips --version` to confirm it's working

Clearer architecture guidance:

• Explicitly state "Most Windows users need the 64-bit (w64) version"
• Add visual cue: "Look for -all- in the filename - this is important!"
• Warn: "Don't download the 'web' or 'light' versions - you need 'all'"

PATH troubleshooting section:

**Common issues:**
- If `vips --version` says "command not found", you need to restart your Command Prompt
- Make sure you added the `bin` subfolder path, not just the main vips folder
- Path should end in `\bin` (e.g., `C:\vips\vips-dev-8.15.5\bin`)

Why this matters: Windows users (especially non-developers) are less familiar with PATH configuration than Linux/Mac users. Clear, step-by-step instructions with screenshots or explicit paths would dramatically reduce setup friction.

Additional Note:

The browser-like launch behavior (similar to Live Server) is unique but works fine. Just mentioning it in case it's intentional or worth documenting for Windows users who might expect a traditional desktop app window.

Happy to test future builds or provide more Windows-specific feedback if helpful.
Thanks,
John

@mholt