Chrome Extension got published - Yay!

Sometime back, I had posted that I had created my first working prototype of a chrome extension. Submitted it to the web store, and it got published!!! So - yay!!! :star_struck: :star_struck:

Show us some lo :heart:e:

tldr;
I built it to solve a problem I kept having during webinar presentations - I’d constantly look down at my notes instead of maintaining eye contact with the camera. This made me appear less confident and created an awkward disconnect with my audience, especially during longer presentations where I’d glance down every few seconds.

The extension keeps your notes visible without breaking that crucial camera eye contact. If anyone here gives presentations or webinars, I’d love for you to check it out and share your feedback!

11 Likes

Have you used Replit to build it? I had bad luck. Can you share prompt to build proper Chrome extension please?

2 Likes

Saweet! I love it! Cool use case.

Yes. It was 80-85% replit and used other tools like Claude and ChatGPT for further refinement.

Thank u!

But it seems to have caught the eye of AI trolls!

1 Like

lol, it happens. Has it been helpful for you?

yes, super useful. built it to solve my own pain point.

2 Likes

That is legit! good work, can you please redirect me so I can create a chrome extension :smiley:

1 Like

Doesn’t work on Mac. Alt+T opens a new tab.

Nice idea though. I’m sure it’s great on PCs.

1 Like

i have been a windows user. let me check if there is someway to mock a MacOS environment

1 Like

Nice! Congrats! I was trying to build a chrome extension as well, but had many issues along the way and then gave up at some point. Do you have any tips?

2 Likes

Everyone’s asking about my development process - plot twist: there’s no magic here!

Started in Replit, built a janky first version, then spent way too much time figuring out why my features were more like “bugs with ambition.” Once it stopped crashing every five minutes, I pushed it to GitHub and moved it into a Claude project.

Then the reviewers swooped in with their “but what about…” questions, so I went back and fixed all the stuff I somehow missed while staring at the code for weeks.

TL;DR: Standard dev cycle - build, break, fix, repeat. No secret sauce, just lots of coffee and iteration! :hot_beverage:

2 Likes

@kody-replit I think this is a huge win area for replit - making these extensions easier to create and deploy. Quick wins for users and enterprises.

3 Likes

There’s probably a proper workflow we can identify and create a video for it.

1 Like