Our mission is to give everyone the power to customize their technology to have the perfect UX. Our first product is a low-code browser extension builder (open-source under AGPLv3)
We recently raised a 3.5M seed from New Enterprise Associates (NEA)
Our mission is to give everyone the power to customize their technology to have the perfect UX. Our first product is a low-code browser extension builder (open-source under AGPLv3)
We recently raised a 3.5M seed from New Enterprise Associates (NEA) and some incredible angel investors including Tableau co-founder Chris Stolte and DataRobot CEO Dan Wright
Open positions:
- Product UI/UX lead (UI/UX designer who can code)
- Community/education lead
- Senior Backend Engineer - API/platform lead
- Senior Front-end Engineer
Our mission is to make it possible for everyone to customize the web to fit the way they work. (Think browser extensions and userscripts, but using sharable lego blocks)
Come be a founding engineer at a company backed by a leading VC and execs of major AI, business intelligence, and edutech companies
Open positions:
- Senior Front-end Engineer
- Senior Backend Engineer - Platform Lead
- Mid-Level Web Designer/Developer
Not an expert on this part, but I'd imagine that problem isn't having an API, it's more that running native executables is the problem if you can't sandbox them or limit their resource consumption. Also, relative to running Javascript, their base resource utilization per tab is significantly worse (especially for Java or .NET-based ones that have a base resource utilization from the VM)
The safety/stability issue comes from the fact that plug-ins (e.g., NPAPI) are native executables
Browsers started dropping support for plug-ins around 2015. However, plug-ins actually held on longer than you might think. Firefox didn't completely drop support for Flash until the beginning of this year