kkevv

Sad to see that FloydHub didn't work out, but you really did build an amazing platform.

Creating and deploying Chrome Extensions is not as straightforward as deploying a webapp (even though CRXs are much simpler). We've been working on helping developers with basic JS skills create custom Chrome Extensions!

Come try building your own extension :)

----

We've been working on a set of templates to show off what you can build as well.

Once you sign in, try out these ready to use templates

- [Stack Overflow Helper](https://hq.extension.dev/template/511)

- [LinkedIn Profile Clipper](https://hq.extension.dev/template/507)

- [Remove distracting websites](https://hq.extension.dev/template/526)

Or use these templates to add your own custom button to popular websites

- [add a custom button to Google Search to search only Reddit](https://hq.extension.dev/template/519)

- [add a button to Tweets to create a Tweet Labeler](https://hq.extension.dev/template/445)

We posted a Show HN 73 days ago about extension.dev. In the 73 days since our last post, we interviewed 70 of you over Zoom. With your help, we designed, built, and shipped V1 of extension.dev. We are now ready to help everyone build and share their own custom extensions.

V1 of extension.dev focuses on helping engineers at companies build Chrome extensions to make their teammates more productive. We've seen early users create context-aware Sidebars to reduce context switching, add buttons to their internal dashboards, and even modify the DOM by removing intrusive elements.

We are excited to invite the HN community to join the developer preview before we make a public release!

Kevin, Will, James

Yeah, pretty much

We are free during the developer preview/beta and plan to have a really generous hobby tier. We are rolling our own Stripe integration down the road for enterprise users!

Selenium is a bit tough because you end up with scripts that are hard for business users to execute. AutoIt and iMacros are solid web automation tools, but they lack the extensibility of a custom solution (to do things like add UI) and are also hard to share with non-technical users across a company.

Another route is to use something like http://alasql.org/ to cache data in localstorage so you can query it instantly. Would a search UX be better, or a text box to directly write SQL over your data?

How did you push through all the people-problems? Was the productivity gained from the extensions the angle you pushed?

If you are down would love to chat more! [email protected]

One of our big use cases is to extend/customize internal tools with UI/data/logic. Could you share more details? If you're more comfortable offline [email protected]

Lmk if you have any questions! I'll be here :)

We are incredibly excited to share what we have been cooking up . After building Chrome Extensions for recruiters and marketers, we got a glimpse of the power of browser extensions. However, we also got a taste of how hard extensions are to create. This led us down a path of exploring whether companies were interested in building custom internal extensions.

We studied hundreds of custom internal extensions that companies are using today. We've seen companies extend legacy internal tools to increase development speed, create context-aware tools that surface info employees need wherever they are. We've even seen extensions add missing features to purchased software. After synthesizing into a few modes, we set out to build an easier way to create internal extensions.

Come say hi! We are excited to meet you and hopefully help you build some extensions too!

Kevin, Will, James