This is a nice explanation and thank you for recording the video! What is not very clear is that Looker Studio and Looker are actually not the same family of products. Studio was designed and built by Google and it resembles Sheets in more ways than it really should. Looker on the other hand was built to compete with Tableau and in many respects it copies those design principles. I think your video sort of skips the concept of connectors in Studio but that's the equivalent of LookML ( or as far as you can get to an equivalent ). Connectors are a good way of controlling data and visualisations and they do give you a lot of customisation. One big downside is that connectors are actually community connectors meaning that you can't just build them for your company (although you can set a price to put people off them). If I had to guess, I'd say that Studio Pro will address the sharing aspect but, even if it does, upgrading from Studio to Studio Pro and then to Looker (full) is not really a straight path. At present, you can keep the data if you store it in BigQuery ( and you probably do even if it's a free tier and you don't have direct access to the actual BigQuery dataset ) but the dashboards will not move from Studio to Looker and your connectors will not be translated to LookML. What I'd be curious to see is if Google finds a way of making that transition 1/2 way painless.
Thanks for the great video! I was struggling to understand the differences here. We are in a moment of deciding whether invest on Looker or remain with our current data analysis structure. This information will be very helpful :)
Thanks for the great video! This is interesting. Basically, Google wants to merge Looker Studio and Looker into something such that it takes advantage of Looker Studio's user base and Looker's function. That said, these two things (Looker Studio and Looker) are quite different. It is hard to imagine how that will be implemented.
