Just tried it. I think this has a lot of potential and I'm planning to revisit in a few months. Right now I'm running into issues with the orchestrator itself, both bugs and difficulty adapting it to my use case. I found myself spending more time fighting the framework than building my actual agent.
We used it a lot some years ago when we built a chatbot for FB Messenger. It was a great surprise. FB analytics was very hidden, but once you got there their product was quite good. Simple to use and gave us 95% of everything we needed to know.
The problem was that you obviously needed to use it with Facebook. As we started building a FB chatbot, that was not an issue, but for any other product it didn't make sense.
We considered:
- Mixpanel was way too expensive for us.
- Google analytics is definitely not a product analytics tool.
- Game Analytics was a good tool, but too much focused on games.
Analytics tools can be very expensive and there weren't many good free alternatives that we were aware of.
Google Analytics is all about web analytics, so you can see traffic sources, visitors, pageviews, custom events, conversion funnels, etc. Primarily your analysis is going to be around traffic sources and how individual pages are performing.
Product analytics tools are a little different in that they’re much more event based and allow for contact/account hierarchies. Ie you can group (and thus track) separate users under a single business entity. They’re also much more feature based, so you’ll primarily be looking at how features are used as opposed to app screens.
It's basically a spam engine. I had to stop using GA because Google, the billion dollar company with a million software engineers, couldn't figure out how to filter out spam from their product.
Basically GA is more of a traffic measuring tool. It doesn't do perfect attribution of events and join them easily for you to build up a picture of the journey the customer takes.
Take for example something like Amplitude which lets you instrument and measure conversion or journey that a user takes across your product.
Recently I've been checking what can be customized in VS Code and my approach was to just check what was modified by the theme. This makes the whole process more intuitive as you can just tweak the settings and see how it would look like.
Hi folks! We are building GitDuck (YC S20) to help software teams talk and collaborate. When we think about the how teams interact (and when we look at how we work as a team), it is normal that many of our interactions consists of showing something and talking about it. We could be sharing the code, a drawing and a lot of times we are sharing a website.
Traditional screen sharing was one way of doing this. Sharing 60 frames of your screen per second and allowing your team to see it. The screen resolution was a problem, because if we had a bad connection, the image quality could reduce.
Another problem was the lack of interactivity and that was too annoying to ignore. Come one, it's 2021 and why were we still doing screen sharing the same way we did in the mid-2000s?
People need to narrate what their team should see ...
"Can you click on that button?"
"What button?"
"Wait, scroll back a little bit"
These tiny frictions build up and the flow of information slow. Screen sharing without interaction is like talking on a walkie-talkie instead of having a real-time conversation.
We want to be able to share any website and allow people to view and control it as if they had opened that website themselves. People can scroll, click on things, see everyone's cursors and even type. It is an interactive screen sharing experience.
What do you think? It would be great to hear your thoughts on this topic!
There’s a lot of stuff to do and configure. You need to set up ssh forwarding and some times it may mean configuring firewalls, ssh keys, or VMs/servers.
GitDuck is just one command, the other peers don’t need to do/install anything and very easy to control permissions (read only vs read+write)
