Forcing Chrome to Install Desktop Apps (Non-PWAs)

Understanding Chrome's PWA Limitation

Chrome’s built-in mechanism for installing web apps relies on specific metadata within the website's code, known as manifest.json. When a site like Google Maps or Twitter has this manifest configured correctly, Chrome offers an "Install" button in the address bar. Sites like Slack and Jira often do not expose this option directly because they are designed to run primarily in the browser or use their own native installers. Forcing a non-PWA to behave exactly like a native app through Chrome alone is technically impossible due to security sandboxing, but we can simulate the result using OS-level shortcuts.

Why Native Installers Differ

Native applications like the desktop version of Slack contain local binaries that communicate with your operating system’s notification center, file system, and hardware accelerators. A web-based shortcut merely opens a Chromium instance with specific flags. While it lacks deep system integration, it provides a distraction-free interface that looks and feels like a separate application, which is sufficient for most productivity workflows.

Creating Dedicated App Windows

The most effective way to replicate the Slack or Jira desktop experience is to create a custom shortcut that launches the web URL in a mode that hides browser chrome elements like tabs, bookmarks, and the address bar. This creates a focused window that behaves like a standalone program.

1. Locate your Chrome shortcut: Find the existing Chrome icon on your desktop or in your Start menu. Right-click it and select Properties.
2. Edit the Target field: In the Target box, you will see the path to chrome.exe followed by some parameters. You need to append specific command-line flags to this path.
3. Add Window Mode Flags: Append the following flags to the end of the target path, ensuring there is a space before the first flag: --app=https://www.slack.com for Slack or --app=https://your-company.atlassian.net for Jira.

The final target string should look something like this:

"C:\Program Files\Google\Chrome\Application\chrome.exe" --app=https://www.slack.com

Click Apply and then OK. When you double-click this new shortcut, Chrome will open in a minimal window containing only the application content, devoid of standard browser navigation controls.

Customizing the Shortcut Experience

To fully mimic a native installation, you should customize the appearance of this shortcut so it does not look like a generic Chrome link. This involves changing the icon and ensuring the shortcut launches independently.

• Change the Icon: Right-click the newly created shortcut and select Properties. Click the Change Icon... button. You can browse to a custom .ico file downloaded from the web service’s brand assets, or use a generic application icon. This visual cue helps differentiate it from regular browsing sessions.
• Set Startup Behavior: If you want the app to launch at login, move the shortcut to your Windows Startup folder. Press Win + R, type shell:startup, and drag the shortcut into this folder.

This approach ensures that when you boot your computer, the app window opens automatically, just like a native background process would. It is important to note that while this method works seamlessly for most single-page applications, some sites may still display small browser indicators if they enforce strict security policies.

Managing Multiple Workspaces

If you use multiple services like Jira, Slack, and GitHub, creating individual shortcuts for each can clutter your desktop. Consider organizing these into a dedicated folder named "Work Apps." Alternatively, you can use Chrome’s profile system. Create a new Chrome Profile specifically for work, and add these --app shortcuts to it. This keeps your personal browsing data separate from your work app windows, enhancing privacy and focus.

Alternative: Using Third-Party Wrappers

If the manual shortcut method feels too technical, consider using third-party tools like Nativefier or Electron-based wrappers. These tools take a URL and bundle it into a true executable file (.exe or .dmg) that runs independently of Chrome. While this offers the closest experience to a native install, it requires downloading external software and managing updates manually. For most users, the Chrome --app flag method remains the safest and most integrated solution within the existing ecosystem.

Frequently Asked Questions

Will these app windows receive system notifications?

Yes, provided the website itself supports web push notifications and you have granted permission in Chrome settings. The app window functions similarly to a normal tab, so browser-level notification permissions apply directly to these focused views.

Can I sync my bookmarks across these app windows?

No, these app windows operate as isolated sessions based on the Chrome profile used to launch them. Bookmarks saved in your main browsing window will not appear in the app window unless you sign into the same Chrome profile in both instances.

Does this method consume more RAM than the native app?

Generally, yes. Running a Chromium instance for each app consumes more memory than a compiled native binary. However, modern browsers optimize this significantly, and the difference is often negligible for typical office tasks compared to the convenience of avoiding separate installers.

How do I update these web apps?

You do not need to update anything. Since these are web applications, any updates pushed by the service provider (Slack, Jira, etc.) are immediately available the next time you load the page. There is no manual update process required.

What happens if the website changes its URL structure?

If the base URL changes, your shortcut will break until you update the --app parameter in the shortcut properties. Always verify the current stable URL of the service before configuring your shortcuts to ensure long-term stability.