[cxam]

The idea behind TAGX.io was to make it easier to share highlights of our football (soccer) video recordings. We have been recording and uploading our games to YouTube over the years and almost everyone that played watched it to see how well they/their team performed. It became an additional discussion point days after the game until the next one. However, it does become tedious having to sit through another hour until you find something special you want to share and discuss, usually this is in the form of “check out the goal 23 minutes in”. I built TAGX to ease this process where someone would go through the video, tag the interesting parts and share it with the group. It was almost like a highlight reel, allowing you to skip through the tagged parts.

This was my winter holiday side project last year and I figured there would be a wider application of this service (conference talks, tutorials, lengthy videos in general) so I decided to polish it up and make it available as a service for others to use. You don’t need to create any account to use it, it’s all client-side and built using Vue.js. It’s hosted on Cloudflare Workers Sites. I wanted to try out Cloudflare Workers/KV, so I ended up building a link shorting feature including authentication/authorisation flow. You can read more about the stack in support -> technology (https://tagx.io/support/general/technology) section.

Here is a tagged video of the AWS re:Invent 2019 event which I shared with someone recently that highlighted some announcements that were of interest to us: https://tagx.io/video/id/Nw-wisbyZPu0LCBk9Tzbn

Following are some development stats for those interested:

- Client-side: ~80 hours (15th Dec 2019 – 7th Jan 2020)

- Server-side: ~30 hours (19th Jan 2019 – 24th Jan 2020)

- Node Experience: 5+ years

- Vue.js Experience: 2+ years

Hope someone finds it useful and any feedback is much appreciated!

[bobosha]

You might want to consider building a chrome extension. Users might have problems recalling your site.

[cxam]

Yea, that's always the issue. An extension would be ideal for desktop users and was considering that as a feature, however, for this initial release, I didn't want to alienate any mobile users that may not have the ability to install an extension. Appreciate your feedback and glad someone has the same idea, definitely makes it easier to prioritise features going forward.