Google Tables

» see tables.area120.google.com as it lived, on the wayback machine

~ the last words ~

i remember reading the launch post for google tables in 2020 and filing it away as a "thing i should try at some point". i never tried it. by then most of the team's project tracking lived in notion and the rest sat in a jira board that nobody loved. google's airtable answer slid right past me, which is also the story of most of area 120.

the product launched in september 2020 as a private beta from area 120, google's in-house incubator. the pitch was a hybrid between a spreadsheet and a small database, with automations layered on top, intended for project tracking and lightweight workflow apps. it was airtable shaped, with a bit of microsoft access in the genealogy. in 2021 it graduated out of the experimental stage and got moved under google cloud as a paid product.

area 120 was the place where this kind of thing was supposed to live. in 2022 google reorganized the incubator and cancelled around half its projects. honestly, in the rounds of layoffs after that, area 120 itself was wound down. tables hung on for a few more years on the google cloud side without much promotion. on september 11, 2025 the team posted the shutdown notice. service was to end after december 16, 2025, with users pushed to sheets or appsheet for migration.

~ the record ~

~ what it actually was ~

tables looked like a sheet with extra columns. each cell could hold a checkbox, a dropdown, a person, a date, a file, the same set of types airtable had taught the market to expect. on top of that sat what google called "bots", small if-this-then-that rules that could move rows, send emails, post to chat. the editor was clean and obviously google-built, in the same family as the modern sheets and the now-dead jamboard frame.

the product never had a free tier that made sense for casual users. the seat pricing put it inside a workspace upsell that competed with airtable's own free tier and with notion's databases. teams who could not get airtable past procurement picked it. teams who already had airtable did not switch. that is not a market position you can hold for long.

~ the area 120 problem ~

area 120 was set up to let small google teams build new consumer products without going through the normal product councils. it shipped tables, the original version of gameSnacks, callJoy, supersonic and a long bench of others. by the time of the 2022 reorganization, the unit was being pushed toward ai-only projects. then the unit was no longer a unit. the catalog of products that had come out of it was left in the awkward space where the parent team had moved on and the new owners did not really want them.

tables ended up in that bucket. the shutdown notice was polite about the migration path. the underlying message was the same one google had sent on stadia and jamboard. the company tried something, the company moved on. five years was actually a decent run for an area 120 graduate.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »