Alternatives to Google Sheets logo

Alternatives to Google Sheets

Airtable, Smartsheet, Google Docs, Google Forms, and Google Drive are the most popular alternatives and competitors to Google Sheets.
1.1K
766
+ 1
15

What is Google Sheets and what are its top alternatives?

Access, create, and edit your spreadsheets wherever you go—from your phone, tablet, or computer.
Google Sheets is a tool in the Spreadsheets Online category of a tech stack.

Top Alternatives to Google Sheets

  • Airtable
    Airtable

    Working with Airtable is as fast and easy as editing a spreadsheet. But only Airtable is backed by the power of a full database, giving you rich features far beyond what a spreadsheet can offer. ...

  • Smartsheet
    Smartsheet

    It is an intuitive online project management tool enabling teams to increase productivity using cloud, collaboration, & mobile technologies. It provides your organization with a powerful work platform that offers exceptional speed to business value ...

  • Google Docs
    Google Docs

    It is a word processor included as part of a free, web-based software office suite offered by Google. It brings your documents to life with smart editing and styling tools to help you easily format text and paragraphs. ...

  • Google Forms
    Google Forms

    It is a cloud-based questionnaire and survey solution with real-time collaboration and powerful tools to customize form questions. It can also be used to create online quizzes. ...

  • Google Drive
    Google Drive

    Keep photos, stories, designs, drawings, recordings, videos, and more. Your first 15 GB of storage are free with a Google Account. Your files in Drive can be reached from any smartphone, tablet, or computer. ...

  • Microsoft Excel
    Microsoft Excel

    Present tables of values arranged in rows and columns that can be manipulated mathematically using basic and complex arithmetic. ...

  • JavaScript
    JavaScript

    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles. ...

  • Git
    Git

    Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. ...

Google Sheets alternatives & related posts

Airtable logo

Airtable

989
866
40
Real-time spreadsheet-database hybrid
989
866
+ 1
40
PROS OF AIRTABLE
  • 19
    Powerful and easy to use
  • 8
    Robust and dynamic
  • 6
    Quick UI Layer
  • 4
    Practical built in views
  • 3
    Robust API documentation
  • 0
    Great flexibility
CONS OF AIRTABLE
    Be the first to leave a con

    related Airtable posts

    Jason Barry
    Cofounder at FeaturePeek · | 10 upvotes · 344.3K views

    If you're a developer using Google Docs or Google Sheets... just stop. There are much better alternatives these days that provide a better user and developer experience.

    At FeaturePeek, we use slite for our internal documents and knowledge tracking. Slite's look and feel is similar to Slack's, so if you use Slack, you'll feel right at home. Slite is great for keeping tabs on meeting notes, internal documentation, drafting marketing content, writing pitches... any long-form text writing that we do as a company happens in Slite. I'm able to be up-to-date with everyone on my team by viewing our team activity. I feel more organized using Slite as opposed to GDocs or GDrive.

    Airtable is also absolutely killer – you'll never want to use Google Sheets again. Have you noticed that with most spreadsheet apps, if you have a tall or wide cell, your screen jumps all over the place when you scroll? With Airtable, you can scroll by screen pixels instead of by spreadsheet cells – this makes a huge difference! It's one of those things that you don't really notice at first, but once you do, you can't go back. This is just one example of the UX improvements that Airtable has to the previous generation of spreadsheet apps – there are plenty more.

    Also, their API is a breeze to use. If you're logged in, the docs fill in values from your tables and account, so it feels personalized to you.

    See more

    I would like to build a community-based customer review platform for a niche industry where users can sign up for a forum, as well as post detailed reviews of their experience with a company/product, including a rating system for pre-selected features. Something like niche.com or areavibes.com with curated information/data, ratings, reviews, and comparison functionalities.

    Is this possible to build using no-code tools? I have read about the possibility of using Webflow with Memberstack, Airtable, and Elfsight through Zapier / Integromat, which may allow for good design and functionality. Is it possible with Bubble or Bildr?

    I have no problems with a bit of a learning curve as long as what I want is possible. Since I have 0 coding experience, I am not sure how to go about it.

    Any advice would be greatly appreciated!

    See more
    Smartsheet logo

    Smartsheet

    102
    115
    0
    An application for collaboration and work management
    102
    115
    + 1
    0
    PROS OF SMARTSHEET
      Be the first to leave a pro
      CONS OF SMARTSHEET
        Be the first to leave a con

        related Smartsheet posts

        Google Docs logo

        Google Docs

        324
        214
        6
        Real-time docs collaboration
        324
        214
        + 1
        6
        PROS OF GOOGLE DOCS
        • 3
          It's simple, but expansive
        • 2
          Free
        • 1
          Fast and simple
        CONS OF GOOGLE DOCS
          Be the first to leave a con

          related Google Docs posts

          Jason Barry
          Cofounder at FeaturePeek · | 10 upvotes · 344.3K views

          If you're a developer using Google Docs or Google Sheets... just stop. There are much better alternatives these days that provide a better user and developer experience.

          At FeaturePeek, we use slite for our internal documents and knowledge tracking. Slite's look and feel is similar to Slack's, so if you use Slack, you'll feel right at home. Slite is great for keeping tabs on meeting notes, internal documentation, drafting marketing content, writing pitches... any long-form text writing that we do as a company happens in Slite. I'm able to be up-to-date with everyone on my team by viewing our team activity. I feel more organized using Slite as opposed to GDocs or GDrive.

          Airtable is also absolutely killer – you'll never want to use Google Sheets again. Have you noticed that with most spreadsheet apps, if you have a tall or wide cell, your screen jumps all over the place when you scroll? With Airtable, you can scroll by screen pixels instead of by spreadsheet cells – this makes a huge difference! It's one of those things that you don't really notice at first, but once you do, you can't go back. This is just one example of the UX improvements that Airtable has to the previous generation of spreadsheet apps – there are plenty more.

          Also, their API is a breeze to use. If you're logged in, the docs fill in values from your tables and account, so it feels personalized to you.

          See more
          Shared insights
          on
          GitHubGitHubGoogle DocsGoogle Docs

          We are trying to find a good tool for internal technical documentation. E.g. playbooks for site operations, or how-to docs on how to use a particular library. The documentation will contain a lot of code/command snippets.

          We currently use Google Docs because of its very good WYSIWYG capabilities, and most importantly, its commenting system that allows us to discuss a particular issue and keep record of that discussion. However, Google docs is not made for code documentation so it's a bit clunky sometimes (e.g. it will capitalize the first letters of sentences etc...).

          We briefly tried the GitHub wiki, but it severely lacked on collaboration/commenting and ease of editing.

          What tools do people recommend for editing internal documentation?

          See more
          Google Forms logo

          Google Forms

          85
          72
          0
          A survey administration app
          85
          72
          + 1
          0
          PROS OF GOOGLE FORMS
            Be the first to leave a pro
            CONS OF GOOGLE FORMS
              Be the first to leave a con

              related Google Forms posts

              Google Drive logo

              Google Drive

              80.3K
              66.8K
              2.1K
              A safe place for all your files
              80.3K
              66.8K
              + 1
              2.1K
              PROS OF GOOGLE DRIVE
              • 505
                Easy to use
              • 326
                Gmail integration
              • 312
                Enough free space
              • 268
                Collaboration
              • 249
                Stable service
              • 128
                Desktop and mobile apps
              • 97
                Offline sync
              • 79
                Apps
              • 74
                15 gb storage
              • 50
                Add-ons
              • 9
                Integrates well
              • 6
                Easy to use
              • 3
                Simple back-up tool
              • 2
                Amazing
              • 2
                Beautiful
              • 2
                Fast upload speeds
              • 2
                The more the merrier
              • 2
                So easy
              • 2
                Wonderful
              • 2
                Linux terminal transfer tools
              • 2
                It has grown to a stable in the cloud office
              • 1
                UI
              • 1
                Windows desktop
              • 1
                G Suite integration
              CONS OF GOOGLE DRIVE
              • 7
                Organization via web ui sucks
              • 2
                Not a real database

              related Google Drive posts

              Tom Klein

              Google Analytics is a great tool to analyze your traffic. To debug our software and ask questions, we love to use Postman and Stack Overflow. Google Drive helps our team to share documents. We're able to build our great products through the APIs by Google Maps, CloudFlare, Stripe, PayPal, Twilio, Let's Encrypt, and TensorFlow.

              See more
              Spenser Coke
              Product Engineer at Loanlink.de · | 9 upvotes · 286.2K views

              When starting a new company and building a new product w/ limited engineering we chose to optimize for expertise and rapid development, landing on Rails API, w/ AngularJS on the front.

              The reality is that we're building a CRUD app, so we considered going w/ vanilla Rails MVC to optimize velocity early on (it may not be sexy, but it gets the job done). Instead, we opted to split the codebase to allow for a richer front-end experience, focus on skill specificity when hiring, and give us the flexibility to be consumed by multiple clients in the future.

              We also considered .NET core or Node.js for the API layer, and React on the front-end, but our experiences dealing with mature Node APIs and the rapid-fire changes that comes with state management in React-land put us off, given our level of experience with those tools.

              We're using GitHub and Trello to track issues and projects, and a plethora of other tools to help the operational team, like Zapier, MailChimp, Google Drive with some basic Vue.js & HTML5 apps for smaller internal-facing web projects.

              See more
              Microsoft Excel logo

              Microsoft Excel

              668
              455
              0
              A spreadsheet program included in the Microsoft Office suite of applications
              668
              455
              + 1
              0
              PROS OF MICROSOFT EXCEL
                Be the first to leave a pro
                CONS OF MICROSOFT EXCEL
                  Be the first to leave a con

                  related Microsoft Excel posts

                  Hey everyone, My users love Microsoft Excel, and so do I. I've been making tools for them in the form of workbooks for years, these tools usually have databases included in the spreadsheets or communicate to free APIs around the web, but now I want to distribute these tools in the form of Excel Add-ins for several reasons.

                  I want these Add-ins to communicate to a personal server to authorize users, read from my databases, and write to them while they're using their Excel environment. I have never built a website, so what would be a good solution for this, considering I'm new to all of these technologies? I know about the existence of Microsoft Azure, Microsoft SharePoint, and Google Sheets, but I don't know how to feel about those.

                  See more

                  I'm a student, and I have a project to build an application (Visual analytics tool) that takes a Microsoft Excel file, cleans the data, and visualizes it. Also, the app should allow the user to filter and interact with it.

                  1- should I make it desktop application or web application? : I'm leaning toward (desktop)

                  2- D3.js OR Python?

                  3- better excel or CSV?

                  I'm a beginner Inspiration for interaction and look of the app: eventflow application.

                  See more
                  JavaScript logo

                  JavaScript

                  351.5K
                  267.6K
                  8.1K
                  Lightweight, interpreted, object-oriented language with first-class functions
                  351.5K
                  267.6K
                  + 1
                  8.1K
                  PROS OF JAVASCRIPT
                  • 1.7K
                    Can be used on frontend/backend
                  • 1.5K
                    It's everywhere
                  • 1.2K
                    Lots of great frameworks
                  • 897
                    Fast
                  • 745
                    Light weight
                  • 425
                    Flexible
                  • 392
                    You can't get a device today that doesn't run js
                  • 286
                    Non-blocking i/o
                  • 237
                    Ubiquitousness
                  • 191
                    Expressive
                  • 55
                    Extended functionality to web pages
                  • 49
                    Relatively easy language
                  • 46
                    Executed on the client side
                  • 30
                    Relatively fast to the end user
                  • 25
                    Pure Javascript
                  • 21
                    Functional programming
                  • 15
                    Async
                  • 13
                    Full-stack
                  • 12
                    Setup is easy
                  • 12
                    Future Language of The Web
                  • 12
                    Its everywhere
                  • 11
                    Because I love functions
                  • 11
                    JavaScript is the New PHP
                  • 10
                    Like it or not, JS is part of the web standard
                  • 9
                    Expansive community
                  • 9
                    Everyone use it
                  • 9
                    Can be used in backend, frontend and DB
                  • 9
                    Easy
                  • 8
                    Most Popular Language in the World
                  • 8
                    Powerful
                  • 8
                    Can be used both as frontend and backend as well
                  • 8
                    For the good parts
                  • 8
                    No need to use PHP
                  • 8
                    Easy to hire developers
                  • 7
                    Agile, packages simple to use
                  • 7
                    Love-hate relationship
                  • 7
                    Photoshop has 3 JS runtimes built in
                  • 7
                    Evolution of C
                  • 7
                    It's fun
                  • 7
                    Hard not to use
                  • 7
                    Versitile
                  • 7
                    Its fun and fast
                  • 7
                    Nice
                  • 7
                    Popularized Class-Less Architecture & Lambdas
                  • 7
                    Supports lambdas and closures
                  • 6
                    It let's me use Babel & Typescript
                  • 6
                    Can be used on frontend/backend/Mobile/create PRO Ui
                  • 6
                    1.6K Can be used on frontend/backend
                  • 6
                    Client side JS uses the visitors CPU to save Server Res
                  • 6
                    Easy to make something
                  • 5
                    Clojurescript
                  • 5
                    Promise relationship
                  • 5
                    Stockholm Syndrome
                  • 5
                    Function expressions are useful for callbacks
                  • 5
                    Scope manipulation
                  • 5
                    Everywhere
                  • 5
                    Client processing
                  • 5
                    What to add
                  • 4
                    Because it is so simple and lightweight
                  • 4
                    Only Programming language on browser
                  • 1
                    Test
                  • 1
                    Hard to learn
                  • 1
                    Test2
                  • 1
                    Not the best
                  • 1
                    Easy to understand
                  • 1
                    Subskill #4
                  • 1
                    Easy to learn
                  • 0
                    Hard 彤
                  CONS OF JAVASCRIPT
                  • 22
                    A constant moving target, too much churn
                  • 20
                    Horribly inconsistent
                  • 15
                    Javascript is the New PHP
                  • 9
                    No ability to monitor memory utilitization
                  • 8
                    Shows Zero output in case of ANY error
                  • 7
                    Thinks strange results are better than errors
                  • 6
                    Can be ugly
                  • 3
                    No GitHub
                  • 2
                    Slow

                  related JavaScript posts

                  Zach Holman

                  Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

                  But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

                  But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

                  Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

                  See more
                  Conor Myhrvold
                  Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 10.7M views

                  How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

                  Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

                  Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

                  https://eng.uber.com/distributed-tracing/

                  (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

                  Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

                  See more
                  Git logo

                  Git

                  290.4K
                  174.5K
                  6.6K
                  Fast, scalable, distributed revision control system
                  290.4K
                  174.5K
                  + 1
                  6.6K
                  PROS OF GIT
                  • 1.4K
                    Distributed version control system
                  • 1.1K
                    Efficient branching and merging
                  • 959
                    Fast
                  • 845
                    Open source
                  • 726
                    Better than svn
                  • 368
                    Great command-line application
                  • 306
                    Simple
                  • 291
                    Free
                  • 232
                    Easy to use
                  • 222
                    Does not require server
                  • 27
                    Distributed
                  • 22
                    Small & Fast
                  • 18
                    Feature based workflow
                  • 15
                    Staging Area
                  • 13
                    Most wide-spread VSC
                  • 11
                    Role-based codelines
                  • 11
                    Disposable Experimentation
                  • 7
                    Frictionless Context Switching
                  • 6
                    Data Assurance
                  • 5
                    Efficient
                  • 4
                    Just awesome
                  • 3
                    Github integration
                  • 3
                    Easy branching and merging
                  • 2
                    Compatible
                  • 2
                    Flexible
                  • 2
                    Possible to lose history and commits
                  • 1
                    Rebase supported natively; reflog; access to plumbing
                  • 1
                    Light
                  • 1
                    Team Integration
                  • 1
                    Fast, scalable, distributed revision control system
                  • 1
                    Easy
                  • 1
                    Flexible, easy, Safe, and fast
                  • 1
                    CLI is great, but the GUI tools are awesome
                  • 1
                    It's what you do
                  • 0
                    Phinx
                  CONS OF GIT
                  • 16
                    Hard to learn
                  • 11
                    Inconsistent command line interface
                  • 9
                    Easy to lose uncommitted work
                  • 7
                    Worst documentation ever possibly made
                  • 5
                    Awful merge handling
                  • 3
                    Unexistent preventive security flows
                  • 3
                    Rebase hell
                  • 2
                    When --force is disabled, cannot rebase
                  • 2
                    Ironically even die-hard supporters screw up badly
                  • 1
                    Doesn't scale for big data

                  related Git posts

                  Simon Reymann
                  Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 9.6M views

                  Our whole DevOps stack consists of the following tools:

                  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
                  • Respectively Git as revision control system
                  • SourceTree as Git GUI
                  • Visual Studio Code as IDE
                  • CircleCI for continuous integration (automatize development process)
                  • Prettier / TSLint / ESLint as code linter
                  • SonarQube as quality gate
                  • Docker as container management (incl. Docker Compose for multi-container application management)
                  • VirtualBox for operating system simulation tests
                  • Kubernetes as cluster management for docker containers
                  • Heroku for deploying in test environments
                  • nginx as web server (preferably used as facade server in production environment)
                  • SSLMate (using OpenSSL) for certificate management
                  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
                  • PostgreSQL as preferred database system
                  • Redis as preferred in-memory database/store (great for caching)

                  The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

                  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
                  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
                  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
                  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
                  • Scalability: All-in-one framework for distributed systems.
                  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
                  See more
                  Tymoteusz Paul
                  Devops guy at X20X Development LTD · | 23 upvotes · 8.6M views

                  Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

                  It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

                  I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

                  We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

                  If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

                  The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

                  Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

                  See more