Reviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
42 reviews
from
External reviews are not included in the AWS star rating for the product.
Quick efficient tool for online documentation
What do you like best about the product?
Different tools to write documentation for different types of projects
What do you dislike about the product?
Too many formats make difficult to make a homogeneous documentation
What problems is the product solving and how is that benefiting you?
Creating, collaborating and publishing online documentation for different kind of projects
A great place to create your API documentation
What do you like best about the product?
Straight out of the box, Readme looks stunning. If you care about providing a satisfying user experience, using a Readme developer hub is the way to go. In my experience using other developer hubs powered by Readme, the server API Reference feature makes it incredibly easy to understand, get samples for and try out various API methods. At our company, we synchronise our client API reference generated in markdown to our Guides section using the Readme API. A handy feature of Readme for providing code samples is Recipes - where you can create a step-by-step walkthrough guide of sample code. I've found these enjoyable to write, and they form an integral part of our feature guides for developers.
What do you dislike about the product?
As great as Readme is, the content editing experience feels quite limited to what markdown can provide. I want more powerful layout features in guides, such as columns. While it's possible to add custom content using HTML/CSS, it would be nicer for Readme to have a more powerful WYSIWYG editor.
When our dashboard got the new editor, I found it stripped many of the features of the previous editor and felt more like an inconvenience. The support team were able to switch us back to the legacy editor.
Images are slow to load on Readme; I would expect some form of optimisation on the platform side. There is no option to host files such as sample projects and demos, which has been a pain point for our team since it's preferable to host everything in one place (on the developer hub).
While the overall website looks fantastic, sometimes minor bugs impede the experience, and it isn't communicated when a release with bug fixes is out. While the suggested edits feature is good, the editing experience is comparably worse than the one provided to editors.
Overall, it's a good platform, but it can feel inconsistent in places - which may be a side-effect of the platform being updated frequently.
When our dashboard got the new editor, I found it stripped many of the features of the previous editor and felt more like an inconvenience. The support team were able to switch us back to the legacy editor.
Images are slow to load on Readme; I would expect some form of optimisation on the platform side. There is no option to host files such as sample projects and demos, which has been a pain point for our team since it's preferable to host everything in one place (on the developer hub).
While the overall website looks fantastic, sometimes minor bugs impede the experience, and it isn't communicated when a release with bug fixes is out. While the suggested edits feature is good, the editing experience is comparably worse than the one provided to editors.
Overall, it's a good platform, but it can feel inconsistent in places - which may be a side-effect of the platform being updated frequently.
What problems is the product solving and how is that benefiting you?
Readme helps us solve creating and organising developer documentation, including guides and recipes, and allows us to sync changes to our API Reference automatically. Readme helps us provide a delightful developer experience and supports us in creating learning resources for our API in various ways.
Slick product, works as advertised.
What do you like best about the product?
Save us a tonne of time on documentation and changelogs.
The admin interface is easy to use, and let's us focus on content.
The changelog feature is cute with subtle graphics for item categorizations, and hence easy to glance.
The admin interface is easy to use, and let's us focus on content.
The changelog feature is cute with subtle graphics for item categorizations, and hence easy to glance.
What do you dislike about the product?
Nothing much, TBH. Do more webinars or QnA sessions for customer success so that we use 90% of its features and not the minimum 50% that we currently do :).
What problems is the product solving and how is that benefiting you?
We don't have to host documentation for our API ourselves.
API documentation has never been easier
What do you like best about the product?
Simple to use, very easy onboarding, super helpful team
What do you dislike about the product?
Cant modify when swagger is used - could be helpful to tweak auto generated docs
What problems is the product solving and how is that benefiting you?
Documentation to our users - saved me weeks of SW developer work
Plain and simple. It works great.
What do you like best about the product?
The ease of use is awesome; it is straightforward and very powerful while being simple to use. I especially like that you can have a molecular design for your Docs; that is, you can make many divisions and levels of information. I also think that something great about Readme is the ease of adding in things different than text (images, tables and Code examples). For example, it's great that you can have multiple versions of the code examples and also the expected result/response.
In general, I think that ReadMe has most of what you could need for creating any Website/Service documentation.
In general, I think that ReadMe has most of what you could need for creating any Website/Service documentation.
What do you dislike about the product?
This really isn't something bad, but I'd love if you could have a side-by-side preview of how the Doc would look, and not have to actually open a new tab to view it.
For the rest of it, for what my colleagues and I use ReadMe for, I genuinely can't find any other things that I don´t like.
For the rest of it, for what my colleagues and I use ReadMe for, I genuinely can't find any other things that I don´t like.
What problems is the product solving and how is that benefiting you?
ReadMe solves our need for a dedicated server instance for our Docs, and further on, it's maintenance. This means that our Development Team can actually concentrate on our Services and not on how the Documentation is shown to our users.
Good software for a simple documentation hub
What do you like best about the product?
The overall structure of the site builder is easy to use. The limited formatting actually helps prevent you from wasting time messing with frivolous settings and encourages concise effective content.
What do you dislike about the product?
Enterprise features are wildly expensive and you have to buy enterprise to use any one of those features. Things like the ability to export your site as a PDF seem like they don't need to be behind that wall.
What problems is the product solving and how is that benefiting you?
Give our customers technical users easy access to API, deployment and implementation info as well as the ability to test APIs all behind a password protected portal.
Readme is the go-to solution for Developer Hubs
What do you like best about the product?
Readme is super easy to onboard and set up. We liked that they support both Swagger-based API docs as well as manually written ones.
This gives the flexibility enough to cater to our business needs.
This gives the flexibility enough to cater to our business needs.
What do you dislike about the product?
Nothing much really.
The only thing we found problematic is that if the API requires a file as input, it doesn't work if the customer directly try it via the Developer Hub.
The only thing we found problematic is that if the API requires a file as input, it doesn't work if the customer directly try it via the Developer Hub.
What problems is the product solving and how is that benefiting you?
It helped us rebuild our client-facing documentation website, including both the user guides as well as developer hubs. Making it super easy for customer to understand and follow
Simple and effective
What do you like best about the product?
Simple and effective markdown editor and guide creation. Automatically builds REST API reference from open API spec, which keeps the reference data update to date at all times. Version control is nice to have as well as new integration are launched.
What do you dislike about the product?
There could be stronger branding elements and more widget options within the guides, mainly to consolidate more general documentation/help guides in a single place. Also an email capture option would be awesome.
What problems is the product solving and how is that benefiting you?
We needed better developer API docs and a simple way to launch them. We also needed a solution that supported both OpenAPI specs as well as custom specs, and Readme.io was able to do both.
Developer documentation is marketing for tech platforms. Readme makes that marketing easy.
What do you like best about the product?
Readme is extremely easy to get use and launch your documentation. If you are a startup, it is a terrific option as you are thinking about how to explain your product's capabilities and how it can be used by your target market.
Their developer tools are excellent and make it very easy for developers using different languages to understand how to use the system and achieve a quicker time to value.
Their developer tools are excellent and make it very easy for developers using different languages to understand how to use the system and achieve a quicker time to value.
What do you dislike about the product?
Readme is built for technology platforms that want to enable customers to self-serve. Readme is also built on this self-serve model - its customer engagement and roadmap is still evolving. But the good news is that its team is very responsive to feedback and actively seeks input from its customer base. This is a platform on the rise.
What problems is the product solving and how is that benefiting you?
SaaS products are complex, and developers are increasingly the buyer of these services. Traditional, wordy marketing websites do not appeal to developers - they prefer to review JSON, XML, or GraphQL directly. Readme makes it very easy to document your service and put your best foot forward with the important audience.
Clear and standardized docs, easy to use and share API documentation
What do you like best about the product?
1. Easy to use.
2. Ease of sharing the request response as curl
3. Headers are set once and is used accross
2. Ease of sharing the request response as curl
3. Headers are set once and is used accross
What do you dislike about the product?
1. Copy Paste of table is difficult - you have to first make it a raw/code and then paste
2. Cannot set two different types to same key i.e object or null
2. Cannot set two different types to same key i.e object or null
What problems is the product solving and how is that benefiting you?
It's fast and easy to showcase API integrations where there are multiple scenarios - especially multiple request and responses
showing 21 - 30