starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-25 08:45:58 +03:00

[GH-ISSUE #507] Sync collection with a cloud storage (e.g: Google drive) #194

New issue

Closed

opened 2026-03-16 13:58:56 +03:00 by kerem · 9 comments

kerem commented

2026-03-16 13:58:56 +03:00

Owner

Originally created by @Aditya94A on GitHub (Jan 19, 2020).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/507

Originally assigned to: @liyasthomas on GitHub.

What is the feature? Postman Teams essentially, without any dedicated backend, we just piggy back off a cloud storage provider.

So, how it would work is basically like:

You're using postwoman, making changes
You decide to simultaneously share collection with your teams, so both frontend and backend (multiple members) can collaborate and get access to the same - always up-to-date - collection without having to export/import over and over again.
User connects with their Google drive
Postwoman collection gets saved in google drive
User gets a unique URL for collection
Anyone can access URL (as per google doc like sharing feature)
Any changes made to collection are synced with the google drive backed collection file.

This would essentially obsolete Postman's biggest use-case.

Check out this application

https://www.draw.io/

Draw.io has a fantastic implementation of this, highly recommend trying out the experience. It's a diagram drawing tool (with not much of a backend for itself, it just piggy backs off of google drive), you can save a diagram to a folder in your google drive, share the diagram link with someone, and you can both work on the same file together.

So, essentially google drive APIs allow you to add real-time collaboration (and other cloud storage goodies) to an app (like Postwoman).

This would literally be a (postman-)killer feature.

Would love to collaborate on this (or anything else in this direction). What are your thoughts on adding collaborative functionalities? (@liyasthomas @jamesgeorge007 @AndrewBastin @NBTX)

Originally created by @Aditya94A on GitHub (Jan 19, 2020). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/507 Originally assigned to: @liyasthomas on GitHub. What is the feature? Postman Teams essentially, without any dedicated backend, we just piggy back off a cloud storage provider. So, how it would work is basically like: 1. You're using postwoman, making changes 2. You decide to simultaneously share collection with your teams, so both frontend and backend (multiple members) can collaborate and get access to the same - always up-to-date - collection without having to export/import over and over again. 3. User connects with their Google drive 4. Postwoman collection gets saved in google drive 5. User gets a unique URL for collection 6. Anyone can access URL (as per google doc like sharing feature) 7. Any changes made to collection are synced with the google drive backed collection file. This would essentially obsolete Postman's biggest use-case. Check out this application https://www.draw.io/ Draw.io has a fantastic implementation of this, highly recommend trying out the experience. It's a diagram drawing tool (with not much of a backend for itself, it just piggy backs off of google drive), you can save a diagram to a folder in your google drive, share the diagram link with someone, and you can both work on the same file together. So, essentially google drive APIs allow you to add real-time collaboration (and other cloud storage goodies) to an app (like Postwoman). This would literally be a (postman-)killer feature. Would love to collaborate on this (or anything else in this direction). What are your thoughts on adding collaborative functionalities? (@liyasthomas @jamesgeorge007 @AndrewBastin @NBTX)

kerem

2026-03-16 13:58:56 +03:00

closed this issue
added the
feature

wip

core
labels

kerem commented

2026-03-16 13:59:12 +03:00

Author

Owner

@liyasthomas commented on GitHub (Jan 19, 2020):

@AdityaAnand1 feature suggestion sounds great! Would love to work on it.

And the mentioned website does the job neatly. Will plan for an MVP, and we would love to add you as a collaborator.

@liyasthomas commented on GitHub (Jan 19, 2020): @AdityaAnand1 feature suggestion sounds great! Would love to work on it. And the mentioned website does the job neatly. Will plan for an MVP, and we would love to add you as a collaborator.

kerem commented

2026-03-16 13:59:17 +03:00

Author

Owner

@liyasthomas commented on GitHub (Jan 19, 2020):

We can certainly make use of Firebase functions, auth, etc for initial prototype. Google sign in seems to be a piece of cake with Firebase Auth.

@liyasthomas commented on GitHub (Jan 19, 2020): We can certainly make use of Firebase functions, auth, etc for initial prototype. Google sign in seems to be a piece of cake with Firebase Auth.

kerem commented

2026-03-16 13:59:23 +03:00

Author

Owner

@Congee commented on GitHub (Jan 20, 2020):

Then I can really ditch Postman.

@Congee commented on GitHub (Jan 20, 2020): Then I can really ditch Postman.

kerem commented

2026-03-16 13:59:28 +03:00

Author

Owner

@liyasthomas commented on GitHub (Jan 20, 2020):

MVP is ready 🎉

checkout auth branch for development: https://github.com/liyasthomas/postwoman/tree/auth

Auth with Google
Auth with GitHub
Add data to Firestore
Delete data from Firestore
UI

@liyasthomas commented on GitHub (Jan 20, 2020): MVP is ready 🎉 checkout `auth` branch for development: https://github.com/liyasthomas/postwoman/tree/auth - [x] Auth with Google - [x] Auth with GitHub - [x] Add data to Firestore - [x] Delete data from Firestore - [x] UI

kerem commented

2026-03-16 13:59:33 +03:00

Author

Owner

@Congee commented on GitHub (Jan 23, 2020):

@liyasthomas you da best!

@Congee commented on GitHub (Jan 23, 2020): @liyasthomas you da best!

kerem commented

2026-03-16 13:59:38 +03:00

Author

Owner

@liyasthomas commented on GitHub (Jan 23, 2020):

I've also add few bugs to be fixed later 😉

@liyasthomas commented on GitHub (Jan 23, 2020): I've also add few bugs to be fixed later 😉

kerem commented

2026-03-16 13:59:43 +03:00

Author

Owner

@Aditya94A commented on GitHub (Jan 25, 2020):

Awesome speed!

Is it now possible for a team to collaborate on the same collection? (Can you add some instructions to the README? It won't be immediately clear to new users)

@Aditya94A commented on GitHub (Jan 25, 2020): Awesome speed! Is it now possible for a team to collaborate on the same collection? (Can you add some instructions to the README? It won't be immediately clear to new users)

kerem commented

2026-03-16 13:59:48 +03:00

Author

Owner

@liyasthomas commented on GitHub (Jan 25, 2020):

Oh no, teams are not yet implemented.
We now have Auth + Sync for a single user account.
Well that's not enough isn't it!
..
..
Okay lets build teams now. ✌️

Joke: Meanwhile share your Auth to your (trusted) teammates!

@liyasthomas commented on GitHub (Jan 25, 2020): Oh no, teams are not yet implemented. We now have Auth + Sync for a single user account. Well that's not enough isn't it! .. .. Okay lets build teams now. ✌️ Joke: Meanwhile share your Auth to your (trusted) teammates!

kerem commented

2026-03-16 13:59:53 +03:00

Author

Owner

@Aditya94A commented on GitHub (Feb 20, 2020):

Do check out the draw.io website @liyasthomas.

Since the current implementation uses firebase storage, the draw.io approach (originally described here as above) might offer significant benefits, including not having to maintain your own backend. And it'd make implementing collaboration (#580) way easier.

@Aditya94A commented on GitHub (Feb 20, 2020): Do check out the draw.io website @liyasthomas. Since the current implementation uses firebase storage, the draw.io approach (originally described here as above) might offer significant benefits, including not having to maintain your own backend. And it'd make implementing collaboration (#580) way easier.

kerem referenced this issue

2026-03-17 00:10:29 +03:00

[PR #194] [MERGED] ⬆️ Bump start-server-and-test from 1.10.3 to 1.10.5 #2474