[Documentation Request] Step-by-step guide for creating Chrome multi-profile apps

[kodama24ek]

Hi! I recently purchased Parall and I really love the concept. However, I am currently struggling to figure out the correct settings to create separate apps for my existing Google Chrome profiles.

I currently have Chrome installed with multiple profiles (Profile 1, Profile 2, Profile 3, Profile 4). My goal is to create a dedicated Parall app for each profile with its own Dock icon, so that clicking it brings the specific profile window to the front (instead of creating a new window every time).

It would be incredibly helpful if you could publish a step-by-step tutorial or a blog post explaining the best practices for this exact use case.

Specifically, I (and probably many others) would love to know:

1. Setup Steps: What are the exact settings (e.g., Data Storage Path, Command Arguments) needed when creating an app for an existing "Profile 1"?
2. Data Migration: Is data migration required to keep my existing bookmarks/extensions, or does Parall just link to the existing profile data? If migration is needed, how do I do it?
3. Coexistence: Can these Parall-generated profile apps coexist with the standard Chrome app seamlessly?

I genuinely believe that a lot of Mac users are looking for this exact solution. Having a clear, official guide would make it so much easier for users to understand, which means we can confidently recommend Parall to others. I'm sure this would help drive more sales too!

Thank you for making such a great app, and I look forward to your response.

[JulyIghor]

Hi, thanks for your feedback!
Parall does separate Chrome data, not its profiles.
To achieve what you need, you have to create Parall shortcuts for the number of your profile count with dedicated data storage paths.

1. run each of them one by one and exit.
2. copy your host Chrome data to each of Parall shortcut data storage on the same paths.

Afterwards, you will get each of Parall shortcuts to display the same list of profiles.
Open each Parall shortcut and remove profiles, keeping one per shortcut.
That way, you will get each Parall shortcut to have one of the profiles you have, and your main Chrome instance will have all of the profiles. Keep in mind those are not synchronized to the main Chrome data storage, but you may symlink those to the host.

I am aware of the need, and I'm working to improve Parall and provide import/sync options for Chrome on the first Parall shortcut launch. And based on your feedback, I'll add FAQ and give more details here later.