Alternatives to Google Keep logo

Alternatives to Google Keep

OneNote, Wunderlist, Todoist, Evernote, and Trello are the most popular alternatives and competitors to Google Keep.
62
57
+ 1
0

What is Google Keep and what are its top alternatives?

It is a note-taking service developed by Google. It is available on the web, and has mobile apps for the Android and iOS mobile operating systems. Keep offers a variety of tools for taking notes, including text, lists, images, and audio.
Google Keep is a tool in the Task Management category of a tech stack.

Top Alternatives to Google Keep

  • OneNote
    OneNote

    Get organized in notebooks you can divide into sections and pages. With easy navigation and search, you’ll always find your notes right where you left them. It gathers users' notes, drawings, screen clippings and audio commentaries. Notes can be shared with other OneNote users over the Internet or a network. ...

  • Wunderlist
    Wunderlist

    It is the easiest way to get stuff done. Whether you’re planning a holiday, sharing a shopping list with a partner or managing multiple work projects, it is here to help you tick off all your personal and professional to-dos. ...

  • Todoist
    Todoist

    It lets you keep track of everything in one place. It gives you the confidence that everything’s organized and accounted for, so you can make progress on the things that are important to you. ...

  • Evernote
    Evernote

    Take notes to a new level with Evernote, the productivity app that keeps your projects, ideas, and inspiration handy across all your digital devices. It helps you capture and prioritize ideas, projects, and to-do lists, so nothing falls through the cracks. ...

  • Trello
    Trello

    Trello is a collaboration tool that organizes your projects into boards. In one glance, Trello tells you what's being worked on, who's working on what, and where something is in a process. ...

  • 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. ...

  • Postman
    Postman

    It is the only complete API development environment, used by nearly five million developers and more than 100,000 companies worldwide. ...

  • Postman
    Postman

    It is the only complete API development environment, used by nearly five million developers and more than 100,000 companies worldwide. ...

Google Keep alternatives & related posts

OneNote logo

OneNote

136
4
A digital notebook for capturing and organizing everything
136
4
PROS OF ONENOTE
  • 1
    Works great with OneDrive
  • 1
    Syncs quickly
  • 1
    Dark mode
  • 1
    Search text in images (OCR)
CONS OF ONENOTE
    Be the first to leave a con

    related OneNote posts

    Wunderlist logo

    Wunderlist

    27
    1
    A cloud-based task management application
    27
    1
    PROS OF WUNDERLIST
    • 1
      Clean, Intuitive, Beautiful
    CONS OF WUNDERLIST
      Be the first to leave a con

      related Wunderlist posts

      Todoist logo

      Todoist

      222
      4
      A task manager & to do list application
      222
      4
      PROS OF TODOIST
      • 4
        The natural language date/time auto-detection is golden
      CONS OF TODOIST
        Be the first to leave a con

        related Todoist posts

        Evernote logo

        Evernote

        238
        21
        Feel organized without the effort
        238
        21
        PROS OF EVERNOTE
        • 5
          Search text in images (OCR)
        • 5
          Checklist
        • 3
          Dark mode
        • 3
          Great mobile app
        • 3
          Syncs quickly
        • 2
          Encrypt Text
        CONS OF EVERNOTE
        • 3
          On life support
        • 2
          No document structure

        related Evernote posts

        Trello logo

        Trello

        43.1K
        3.7K
        Your entire project, in a single glance
        43.1K
        3.7K
        PROS OF TRELLO
        • 715
          Great for collaboration
        • 628
          Easy to use
        • 573
          Free
        • 375
          Fast
        • 347
          Realtime
        • 237
          Intuitive
        • 215
          Visualizing
        • 169
          Flexible
        • 126
          Fun user interface
        • 83
          Snappy and blazing fast
        • 30
          Simple, intuitive UI that gets out of your way
        • 27
          Kanban
        • 21
          Clean Interface
        • 18
          Easy setup
        • 18
          Card Structure
        • 17
          Drag and drop attachments
        • 11
          Simple
        • 10
          Markdown commentary on cards
        • 9
          Lists
        • 9
          Integration with other work collaborative apps
        • 8
          Satisfying User Experience
        • 8
          Cross-Platform Integration
        • 7
          Recognizes GitHub commit links
        • 6
          Easy to learn
        • 5
          Great
        • 4
          Better than email
        • 4
          Versatile Team & Project Management
        • 3
          and lots of integrations
        • 3
          Trello’s Developmental Transparency
        • 3
          Effective
        • 2
          Easy
        • 2
          Powerful
        • 2
          Agile
        • 2
          Easy to have an overview of the project status
        • 2
          flexible and fast
        • 2
          Simple and intuitive
        • 1
          Name rolls of the tongue
        • 1
          Customizable
        • 1
          Email integration
        • 1
          Personal organisation
        • 1
          Nice
        • 1
          Great organizing (of events/tasks)
        • 0
          Easiest way to visually express the scope of projects
        CONS OF TRELLO
        • 5
          No concept of velocity or points
        • 4
          Very light native integrations
        • 2
          A little too flexible

        related Trello posts

        Johnny Bell

        So I am a huge fan of JIRA like #massive I used it for many many years, and really loved it, used it personally and at work. I would suggest every new workplace that I worked at to switch to JIRA instead of what I was using.

        When I started at #StackShare we were using a Trello #Kanban board and I was so shocked at how easy the workflow was to follow, create new tasks and get tasks QA'd and deployed. What was so great about this was it didn't come with all the complexity of JIRA. Like setting up a project, user rules etc. You are able to hit the ground running with Trello and get tasks started right away without being overwhelmed with the complexity of options in JIRA

        With a few TrelloPowerUps we were easily able to add GitHub integration and storyPoints to our cards and thats all we needed to get a really nice agile workflow going.

        I'm not saying that JIRA is not useful, I can see larger companies being able to use the JIRA features and have the time to go through all the complex setup to get a really good workflow going. But for smaller #Startups that want to hit the ground running Trello for me is the way to go.

        In saying that what I would love Trello to implement is to allow me to create custom fields. Right now we just have a Description field. So I am adding User Stories & How To Test in the Markdown of the Description if I could have these as custom fields then my #Agile workflow would be complete.

        #StackDecisionsLaunch

        See more
        Francisco Quintero
        Tech Lead at Dev As Pros · | 13 upvotes · 1.8M views

        For Etom, a side project. We wanted to test an idea for a future and bigger project.

        What Etom does is searching places. Right now, it leverages the Google Maps API. For that, we found a React component that makes this integration easy because using Google Maps API is not possible via normal API requests.

        You kind of need a map to work as a proxy between the software and Google Maps API.

        We hate configuration(coming from Rails world) so also decided to use Create React App because setting up a React app, with all the toys, it's a hard job.

        Thanks to all the people behind Create React App it's easier to start any React application.

        We also chose a module called Reactstrap which is Bootstrap UI in React components.

        An important thing in this side project(and in the bigger project plan) is to measure visitor through out the app. For that we researched and found that Keen was a good choice(very good free tier limits) and also it is very simple to setup and real simple to send data to

        Slack and Trello are our defaults tools to comunicate ideas and discuss topics, so, no brainer using them as well for this project.

        See more
        Google Docs logo

        Google Docs

        324
        6
        Real-time docs collaboration
        324
        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 · 348.8K 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
          Michael Videlgauz
          Shared insights
          on
          Google DocsGoogle DocsConfluenceConfluence

          Hello community, I am looking for a self-hosted online document management solution. One that covers all my needs is Confluence but it is currently not affordable for my team. Key requirements are RTL support, WYSIWYG Editing (Word-like interface as much as possible), Concurrent Editing (the best experience I have with Google Docs where I can even see who else is currently editing a document) with conflict resolution, versioning (view history and switch between versions), PDF and Word export, complex tables, and some others, full list here in column "A". I found XWIKI covering all my requirements (including those "bonus features" that I didn't list here) except one - RTL. Here a hack is suggested to address this issues but I would prefer not to go with any hacks. I myself am ready to contribute to an open source development but other people who (hopefully) will use this tool are not software engineers and this fact must be kept in mind... Any suggestions are greatly appreciated!

          See more
          Postman logo

          Postman

          94.5K
          1.8K
          Only complete API development environment
          94.5K
          1.8K
          PROS OF POSTMAN
          • 490
            Easy to use
          • 369
            Great tool
          • 276
            Makes developing rest api's easy peasy
          • 156
            Easy setup, looks good
          • 144
            The best api workflow out there
          • 53
            It's the best
          • 53
            History feature
          • 44
            Adds real value to my workflow
          • 43
            Great interface that magically predicts your needs
          • 35
            The best in class app
          • 12
            Can save and share script
          • 10
            Fully featured without looking cluttered
          • 8
            Collections
          • 8
            Option to run scrips
          • 8
            Global/Environment Variables
          • 7
            Shareable Collections
          • 7
            Dead simple and useful. Excellent
          • 7
            Dark theme easy on the eyes
          • 6
            Awesome customer support
          • 6
            Great integration with newman
          • 5
            Documentation
          • 5
            Simple
          • 5
            The test script is useful
          • 4
            Saves responses
          • 4
            This has simplified my testing significantly
          • 4
            Makes testing API's as easy as 1,2,3
          • 4
            Easy as pie
          • 3
            API-network
          • 3
            I'd recommend it to everyone who works with apis
          • 3
            Mocking API calls with predefined response
          • 2
            Now supports GraphQL
          • 2
            Postman Runner CI Integration
          • 2
            Easy to setup, test and provides test storage
          • 2
            Continuous integration using newman
          • 2
            Pre-request Script and Test attributes are invaluable
          • 2
            Runner
          • 2
            Graph
          • 1
            <a href="http://fixbit.com/">useful tool</a>
          CONS OF POSTMAN
          • 10
            Stores credentials in HTTP
          • 9
            Bloated features and UI
          • 8
            Cumbersome to switch authentication tokens
          • 7
            Poor GraphQL support
          • 5
            Expensive
          • 3
            Not free after 5 users
          • 3
            Can't prompt for per-request variables
          • 1
            Import swagger
          • 1
            Support websocket
          • 1
            Import curl

          related Postman posts

          Noah Zoschke
          Engineering Manager at Segment · | 30 upvotes · 3M views

          We just launched the Segment Config API (try it out for yourself here) — a set of public REST APIs that enable you to manage your Segment configuration. A public API is only as good as its #documentation. For the API reference doc we are using Postman.

          Postman is an “API development environment”. You download the desktop app, and build API requests by URL and payload. Over time you can build up a set of requests and organize them into a “Postman Collection”. You can generalize a collection with “collection variables”. This allows you to parameterize things like username, password and workspace_name so a user can fill their own values in before making an API call. This makes it possible to use Postman for one-off API tasks instead of writing code.

          Then you can add Markdown content to the entire collection, a folder of related methods, and/or every API method to explain how the APIs work. You can publish a collection and easily share it with a URL.

          This turns Postman from a personal #API utility to full-blown public interactive API documentation. The result is a great looking web page with all the API calls, docs and sample requests and responses in one place. Check out the results here.

          Postman’s powers don’t end here. You can automate Postman with “test scripts” and have it periodically run a collection scripts as “monitors”. We now have #QA around all the APIs in public docs to make sure they are always correct

          Along the way we tried other techniques for documenting APIs like ReadMe.io or Swagger UI. These required a lot of effort to customize.

          Writing and maintaining a Postman collection takes some work, but the resulting documentation site, interactivity and API testing tools are well worth it.

          See more
          Simon Reymann
          Senior Fullstack Developer at QUANTUSflow Software GmbH · | 27 upvotes · 5.1M views

          Our whole Node.js backend stack consists of the following tools:

          • Lerna as a tool for multi package and multi repository management
          • npm as package manager
          • NestJS as Node.js framework
          • TypeScript as programming language
          • ExpressJS as web server
          • Swagger UI for visualizing and interacting with the API’s resources
          • Postman as a tool for API development
          • TypeORM as object relational mapping layer
          • JSON Web Token for access token management

          The main reason we have chosen Node.js over PHP is related to the following artifacts:

          • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
          • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
          • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
          • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
          See more
          Postman logo

          Postman

          94.5K
          1.8K
          Only complete API development environment
          94.5K
          1.8K
          PROS OF POSTMAN
          • 490
            Easy to use
          • 369
            Great tool
          • 276
            Makes developing rest api's easy peasy
          • 156
            Easy setup, looks good
          • 144
            The best api workflow out there
          • 53
            It's the best
          • 53
            History feature
          • 44
            Adds real value to my workflow
          • 43
            Great interface that magically predicts your needs
          • 35
            The best in class app
          • 12
            Can save and share script
          • 10
            Fully featured without looking cluttered
          • 8
            Collections
          • 8
            Option to run scrips
          • 8
            Global/Environment Variables
          • 7
            Shareable Collections
          • 7
            Dead simple and useful. Excellent
          • 7
            Dark theme easy on the eyes
          • 6
            Awesome customer support
          • 6
            Great integration with newman
          • 5
            Documentation
          • 5
            Simple
          • 5
            The test script is useful
          • 4
            Saves responses
          • 4
            This has simplified my testing significantly
          • 4
            Makes testing API's as easy as 1,2,3
          • 4
            Easy as pie
          • 3
            API-network
          • 3
            I'd recommend it to everyone who works with apis
          • 3
            Mocking API calls with predefined response
          • 2
            Now supports GraphQL
          • 2
            Postman Runner CI Integration
          • 2
            Easy to setup, test and provides test storage
          • 2
            Continuous integration using newman
          • 2
            Pre-request Script and Test attributes are invaluable
          • 2
            Runner
          • 2
            Graph
          • 1
            <a href="http://fixbit.com/">useful tool</a>
          CONS OF POSTMAN
          • 10
            Stores credentials in HTTP
          • 9
            Bloated features and UI
          • 8
            Cumbersome to switch authentication tokens
          • 7
            Poor GraphQL support
          • 5
            Expensive
          • 3
            Not free after 5 users
          • 3
            Can't prompt for per-request variables
          • 1
            Import swagger
          • 1
            Support websocket
          • 1
            Import curl

          related Postman posts

          Noah Zoschke
          Engineering Manager at Segment · | 30 upvotes · 3M views

          We just launched the Segment Config API (try it out for yourself here) — a set of public REST APIs that enable you to manage your Segment configuration. A public API is only as good as its #documentation. For the API reference doc we are using Postman.

          Postman is an “API development environment”. You download the desktop app, and build API requests by URL and payload. Over time you can build up a set of requests and organize them into a “Postman Collection”. You can generalize a collection with “collection variables”. This allows you to parameterize things like username, password and workspace_name so a user can fill their own values in before making an API call. This makes it possible to use Postman for one-off API tasks instead of writing code.

          Then you can add Markdown content to the entire collection, a folder of related methods, and/or every API method to explain how the APIs work. You can publish a collection and easily share it with a URL.

          This turns Postman from a personal #API utility to full-blown public interactive API documentation. The result is a great looking web page with all the API calls, docs and sample requests and responses in one place. Check out the results here.

          Postman’s powers don’t end here. You can automate Postman with “test scripts” and have it periodically run a collection scripts as “monitors”. We now have #QA around all the APIs in public docs to make sure they are always correct

          Along the way we tried other techniques for documenting APIs like ReadMe.io or Swagger UI. These required a lot of effort to customize.

          Writing and maintaining a Postman collection takes some work, but the resulting documentation site, interactivity and API testing tools are well worth it.

          See more
          Simon Reymann
          Senior Fullstack Developer at QUANTUSflow Software GmbH · | 27 upvotes · 5.1M views

          Our whole Node.js backend stack consists of the following tools:

          • Lerna as a tool for multi package and multi repository management
          • npm as package manager
          • NestJS as Node.js framework
          • TypeScript as programming language
          • ExpressJS as web server
          • Swagger UI for visualizing and interacting with the API’s resources
          • Postman as a tool for API development
          • TypeORM as object relational mapping layer
          • JSON Web Token for access token management

          The main reason we have chosen Node.js over PHP is related to the following artifacts:

          • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
          • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
          • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
          • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
          See more