It's the future of team collaboration. Or at least I think so.
If you have been in a development team, you’ll understand the struggle. Instead of sending endless screenshots or long screen recordings trying to explain something to your designer or manager, you can instead use TagU to leave comments on the web.
That means, you can click on ANY website, anywhere on the web, and it will open a text box. Simply write your instructions, and tag your intended recipient. Okay okay, that may sound confusing, but here’s an example.
Example 1: On your landing page, you want a certain piece of text to become blue. Instead of taking a screenshot, annotating your idea, and sending it to your developer, you just use TagU. Using TagU, you click on the desired text, write "@developer can you make this text blue?" and it automatically sends to your developer. They get a notification of your message and can make changes quickly.
Sounds amazing right?
Well if you think so, join the waitlist and help us turn this idea into a reality!
The idea seems to make it faster to push, but does it reduce work, or does it increase it?
I'm thinking end-to-end time, as that's what to measure.
By pushing, perhaps 'speed convenient' for the pusher, what incentive is there to put a meaningful message? Is the incentive greater or less than had it been in an email or other tracking tool already in use? Is tagging a page clearer than a screenshot and URL with a giant red box around what a problem is?
For tracking, is someone going to have to document a change? If a 'push' went into a tracking tool from the start, this cost would be front-loaded. If from this method of pushing, is this cost offloaded from the pusher rather than removed? If a cost of pushing is reduced, will the number of unnecessary pushes increase? Is 'necessary' to again negotiated through email or other threaded back-and-forth, and will this increase that?
Is there a social annotation aspect, like hypthes.is-like comments in the tagging? If so, is there a benefit vs. a cost? I could see this working very well on a 'dev' site for example that's under active change, with 'social' in the comments (and wildly imagining a 'rewind' conversation function like Google Wave back in the day).
Does it reduce end-to-end workload, or discover value somehow? That'd be my key barometer.
What happens with SPAs? Because the page is constantly changing. The tag is smart enough to be displayed only when it is needed? If so, it could be hard for the developer search the tag in SPAs with more than 3 “pages”
From the landing page, I don't understand what it does:
> Goodbye to endless screenshots. Hello to productive communication.
This made it a bit more clear:
> That means, you can click on ANY website, anywhere on the web, and it will open a text box. Simply write your instructions, and tag your intended recipient. Okay okay, that may sound confusing, but here’s an example.
But I don't understand how it is easier than making a screenshot and sending it via Slack with a comment about the screenshot.
4 comments
[ 4.3 ms ] story [ 22.8 ms ] threadIt's the future of team collaboration. Or at least I think so.
If you have been in a development team, you’ll understand the struggle. Instead of sending endless screenshots or long screen recordings trying to explain something to your designer or manager, you can instead use TagU to leave comments on the web.
That means, you can click on ANY website, anywhere on the web, and it will open a text box. Simply write your instructions, and tag your intended recipient. Okay okay, that may sound confusing, but here’s an example.
Example 1: On your landing page, you want a certain piece of text to become blue. Instead of taking a screenshot, annotating your idea, and sending it to your developer, you just use TagU. Using TagU, you click on the desired text, write "@developer can you make this text blue?" and it automatically sends to your developer. They get a notification of your message and can make changes quickly.
Sounds amazing right?
Well if you think so, join the waitlist and help us turn this idea into a reality!
Waitlist: https://tagu.vercel.app/
I'm thinking end-to-end time, as that's what to measure.
By pushing, perhaps 'speed convenient' for the pusher, what incentive is there to put a meaningful message? Is the incentive greater or less than had it been in an email or other tracking tool already in use? Is tagging a page clearer than a screenshot and URL with a giant red box around what a problem is?
For tracking, is someone going to have to document a change? If a 'push' went into a tracking tool from the start, this cost would be front-loaded. If from this method of pushing, is this cost offloaded from the pusher rather than removed? If a cost of pushing is reduced, will the number of unnecessary pushes increase? Is 'necessary' to again negotiated through email or other threaded back-and-forth, and will this increase that?
Is there a social annotation aspect, like hypthes.is-like comments in the tagging? If so, is there a benefit vs. a cost? I could see this working very well on a 'dev' site for example that's under active change, with 'social' in the comments (and wildly imagining a 'rewind' conversation function like Google Wave back in the day).
Does it reduce end-to-end workload, or discover value somehow? That'd be my key barometer.
> Goodbye to endless screenshots. Hello to productive communication.
This made it a bit more clear:
> That means, you can click on ANY website, anywhere on the web, and it will open a text box. Simply write your instructions, and tag your intended recipient. Okay okay, that may sound confusing, but here’s an example.
But I don't understand how it is easier than making a screenshot and sending it via Slack with a comment about the screenshot.