Live data from Hacker News

Tables: Tracking work for teams

blog.google

331–340 of 375 posts

Re: Tables: Tracking work for teams

#331

Earlier quoted context omitted.

If HN is interested in the success/failure of products & services, product-market fit and such, then what Google have done to themselves is a fascinating phenomenon. In the past, many companies have had "not great" reputations for supporting products, but surely Google have taken it to level not seen before. The fact that pretty much all of their products live in the cloud rather than being software that can continue…

> If HN is interested in the success/failure of products & services, product-market fit and such, then what Google have done to themselves is a fascinating phenomenon. Sure, that's a reason discussion of the phenomenon is appropriate for HN, just as discussion of AI-driven automated spamming of message boards as a marketing technique might be. (Though, even then, not an appropriate thing to derail every thread in whi…

It is a necessary lens to view any new Google product through, though. There is a real risk that they will abandon anything they launch.

Re: Tables: Tracking work for teams

#332

Earlier quoted context omitted.

> If HN is interested in the success/failure of products & services, product-market fit and such, then what Google have done to themselves is a fascinating phenomenon. Sure, that's a reason discussion of the phenomenon is appropriate for HN, just as discussion of AI-driven automated spamming of message boards as a marketing technique might be. (Though, even then, not an appropriate thing to derail every thread in whi…

It is a necessary lens to view any new Google product through, though. There is a real risk that they will abandon anything they launch.

> It is a necessary lens to view any new Google product through, though.

No, it's not.

> There is a real risk that they will abandon anything they launch.

There is a real risk that any company will do that, either by internal choice, or by change of plan due to acquisition, or by business failures. It really isn't necessary or helpful for people who have no interest in Google products because of their view of the brand (whether for this reason or any other) to pollute every discussion thread about a Google product with this.

Re: Tables: Tracking work for teams

#333
post #254

Earlier quoted context omitted.

Amazing work. This may be a very obvious question, but just to be clear, does the github repo offer the same as the hosted SaaS version? Meaning can I host this internally and play around with it as a proof-of-concept at work?

Yes you can! The open source version offers the same functionality as the SaaS version. If you have Docker installed on your computer you can follow the demo environment tutorial at https://baserow.io/docs/guides/demo-environment to test out a copy locally.

Great, thanks! Will definitely have to give it a whirl when I free some time on my schedule

Re: Tables: Tracking work for teams

#334
post #314
post #299

Earlier quoted context omitted.

There have been well more than 205 failed startups in the last 10 years and so many more since G started. Google kill count is high but startup failure is much much higher

The difference is that originally there was a higher likelihood of trying out a Google product than a random startup's. Now that equation is flipped- I'd rather try a random startup's product than a Google one- at least the startup is going to live and die on making that product a success. Google? It has to be a massive world spanning success or its a guaranteed goner.

A VC-funded startup needs to be a runaway success. A million dollar idea isn't even going to get funding in the valley.

Re: Tables: Tracking work for teams

#335
Interesting, but it seems a bit behind compared to the market. I'd much use ClickUp as the UI is much more appealing. Notion/Airtable too. Feels a bit like Chat vs. Slack. I'd rather use Slack any day of the week because rather than just one Google team the entire company is working on improvements and will do better over time. Not trying to s* all over Google, but there are better options for that price point.

Re: Tables: Tracking work for teams

#336
post #320

Earlier quoted context omitted.

Hey jbm, Tables PM here, your comment definitely resonated with me. Fun fact: I'm Canadian! :P On your point though: as my own opinion, there's some very smart people here trying to make sure we're doing things in a safe way that protects both our users and our team, and so sometimes we're asked to start small. As a result, we're doing what we can to offer something useful for people and businesses during these covid…

I would be very interested to hear more about why, specifically, Canadians (like you and me) are seen as potentially unsafe users. (Regardless of that, congratulations on your launch and good luck!)

Thanks! Very much appreciate the kind words. :)

Yeah, to give you my perspective on this for a second: the reality is that the rules for how we work with and protect user data continues to evolve and become more nuanced with the different regulations from different countries. Not to mention, taking payments in different countries and currencies has a lot of implications! For every country we release to, there's a bunch of potentially new rules to follow, so it's a lot simpler and safer to do it with just one country first, get it right, and then expand after that. In my experience, there's no particular opinion that users from a particular country are "unsafe," but it's more about whether we have enough time and people to make sure we're doing things right by our users.

Hope that gives you a little insight into this and how we think about it!

Re: Tables: Tracking work for teams

#337

Earlier quoted context omitted.

Hey there! I'm the Tables PM and your comment caught my eye. I really appreciate that feedback for us, and we're really hoping to make it as useful as possible for you and others! :) As prlambert@ mentioned in another comment, we're kinda like a startup and if things go well, the goal is graduate into larger parts of Google. A point of clarification on the free tier: we're offering 1000 rows per table --an individual…

Could you enable it for Mexico? Don't see the point in limiting the product. I need something just like this.

Hey there! I'll point you to a similar comment and response I gave for a fellow non-American who asked the same question: https://news.ycombinator.com/item?id=24556244.

tl;dr is we'd love to and we're working on it! I'm glad to hear you're interested in Tables, we'll try to get it to you as soon as we can.

Re: Tables: Tracking work for teams

#338

As a product, this looks super-cool. However, I've got to be honest: while I'd play around with it while it's part of Area 120, there's no way I'd use it in a business until it officially became part of G Suite, as a core service . If Keep and Tasks are core services, then this needs to be too. That becomes a guarantee that it'll stick around basically forever. So it's very exciting to see Google launch something lik…

> Since when is beta software charged for?

Since forever. I will concede that the cool kids call it "early access" these days, however.

Re: Tables: Tracking work for teams

#339

Earlier quoted context omitted.

Hey there! I'm the Tables PM and your comment caught my eye. I really appreciate that feedback for us, and we're really hoping to make it as useful as possible for you and others! :) As prlambert@ mentioned in another comment, we're kinda like a startup and if things go well, the goal is graduate into larger parts of Google. A point of clarification on the free tier: we're offering 1000 rows per table --an individual…

Cool. I would migrate my personal bookmarks to Table, and you how it can grow through the time, actually I have 6k records. Another real use case is tracking compliance recommendations for simple teams operating in 300 locations around the world, I would assign 200 tasks per office that staff must follow up each 6 months for 4 periods, just need to use a couple of process flow triggers in order to make it operative.…

That's really helpful to hear, thanks for the examples. I definitely agree that there's potential for supporting use cases beyond just simple work tracking, and into more advanced workflows, and I'm hoping that we'll be able to make Tables useful for some of those use cases in the future too.

Thanks for the kind words, and I hope Tables will help people and businesses in positive ways as well! From my perspective, we just want to offer a decent option for users who want to track team work within the Google ecosystem, especially during this time with covid forcing many businesses to digitize and work remotely.

Thanks for sharing those use cases and we'll take that feedback on the limits back to the team.

Re: Tables: Tracking work for teams

#340
post #292

Earlier quoted context omitted.

> To my knowledge, nothing majorly successful or long-term supported has ever come out of Area 120. Instead try evaluating the success of Area 120 by the number of Google staff members who have had their "incredible journey" itch scratched and then returned to a product or infrastructure team at Google when their Area 120 project is EOL'ed. From a corporate perspective, it's worth spending some money on throw-away pr…

I definitely understand why it benefits Google. But I don't see why a user should ever bother with an Area 120 project.

Agreed
Post reply on HN