Integrate custom JS extensions?
SUMMARY (your need in one sentence) As a developer I would like to be able to integrate custom JS extensions. GIVE US CONTEXT (tell us about the current experience) I like to alter some of the webapps I use by simple JS extentions. The fact that this currently isn’t possible prevents me from fully switching from Chrome to Station PROVIDE DETAILS (tell us what you are looking to change) I’d like to be able to integrate extensions per webapp, being able to select 1 js file would already be great. DESCRIBE THE IMPACT (how would it change your experience) It would allow me to use the web apps precisely as I want to.
Electron webview partitions
I installed Station today and have been very impressed with the ootb functionality. One thing that seems not too difficult to add that I think would be extremely useful is a way to group related app instances into a persistent webview partition. The main problem with not being able to do this is the fact that all apps load in the Electron session.defaultSession, thus preventing users from logging in as different users to multiple instances of an app that does not support multiple instances (e.g. Microsoft Teams). It seems like it would be a fairly simple undertaking to take advantage of the 'partition' functionality already present in the Electron webview component to implement this. All that would be needed is a way to assign an app instance to a group (could literally just be another setting textbox for the app instance). Then, you could set the <webview partition="persist:[group-name]".../> attribute when that app instance is opened. This will cause only the app instances with the same [group-name] to use the same session, effectively isolating them from all other app instances of the same type. All un-grouped apps could continue to use session.defaultSession, preserving the existing functionality. To prove that this concept works, I unpacked app.asar, modified the mainRender.js file to add the partition attribute with a random string value to the webview element, repacked and substituted the updated file. I was able to login multiple times to app instances that used the same login provider and maintain distinct sessions. Of course, this rudimentary solution unconditionally isolates every app from every other app which is undesirable, but I think it serves as a good poc starting point. Any resistance to this? If it is just lack of resources I wouldn't mind putting a fork together to demo the functionality.
What engine runs the cards content
What sits underneath those cards? chromium, something based on FF?
Why are extensions so hard to implement? What is the technical difficulty exactly?
Why are extensions so hard to implement? What is the technical difficulty exactly? I am aware that Station is built on top of electron. And electron is a modified Chromium. Case and Point: Many modified chromium browsers support extensions out of the box. I would be really interested to learn what obstacles are there at the moment to prevent you from supporting all the extensions. (even all the apps) What is the technical difficulty exactly? /Discuss
:eyes: Station is looking for beta-testers of its SDK
Some features of Station have been designed to support extensions via a SDK and that’ll multiply the value for the end user (ie you!). For instance, we recently worked on the Quick-Switch, and gradually added support for [Slack](https://community.getstation.com/t/request-for-feedback- slack-integration-in-the-quick-switch/3185/), [Google Drive](https://community.getstation.com/t/request-for-feedback-google-drive- integration-with-the-quick-switch/3263) and, recently, Notion. You can search and jump quickly to your most used Slack channels, Google Drive documents or Notion pages. [ 2maDA2oxOD.gif1150×958 2.82 MB ](https://community.getstation.com/uploads/default/original/2X/0/06dabbe4f85c255c0d4d6b59508c031a3e41b56c.gif "2maDA2oxOD.gif") It would be great to have similar superpowers with Google Calendar events, Asana’s tasks, Jira issues and so on, right? We plan to open the SDK that powers Slack, Google Drive and Notion integration in Station, and let developers add integration to the Quick-Switch. We are looking for beta-testers of this SDK and developers willing to give their feedback on how this newly born SDK should be extended. If interested, [please fill this form](https://stationapp.typeform.com/to/fSeYsJ).
Station + developers = ideas gathering
We have on our roadmap the project to open Station platform to developers (we sometimes internally refer to this project as “Station extension SDK”). As of today, we haven’t worked on this nor clearly defined what it would look like. Nevertheless, we received some interest of such possibilities, so, I’m opening this topic now to gather ideas and discussion around opening Station platform to developer. As developer, how would you envision working on Station? What parts of the product should be open? What are the ideas of project you think would make sense for you? On our side, here the few ideas we have in mind: give access to Station thru a extension system (similar to Chrome extension) with a SDK that’d allow to plug into the different parts of Station get inspiration from Atom code editor plugin architecture add the possibility to plug into the quick-switch / search (`Cmd+T`), notification center, the subdock (hover-menu on dock icons) add a widget system Let us know your thoughts!