Apiary vs ReadMe.io: What are the differences?
What is Apiary? Integrated API documentation, prototyping and testing. It takes more than a simple HTML page to thrill your API users. The right tools take weeks of development. Weeks that apiary.io saves.
What is ReadMe.io? Beautiful documentation made easy. Collaborative Developer Hubs.
Apiary and ReadMe.io can be primarily classified as "Documentation as a Service &" tools.
Some of the features offered by Apiary are:
- Documentation- Organized around resources, code samples with syntax highlight, easy to explore.
- Inspector- Users can make API calls through apiary.io, we show them how they differ from documentation.
- Community- Opensource your API documentation on GitHub. The right channel between developers on both side of the API.
On the other hand, ReadMe.io provides the following key features:
- Collaboration - Crowdsource your docs! Users can keep docs current by suggesting changes.
- API Explorer - Let users play with your API right inside the documentation.
- GitHub Sync - Keep auto-generated reference docs synced with your actual code.
"Easy to use" is the primary reason why developers consider Apiary over the competitors, whereas "Great UI" was stated as the key factor in picking ReadMe.io.
Sellsuki, TestLegends, and Frank and Oak are some of the popular companies that use Apiary, whereas ReadMe.io is used by UNION, ReadMe.io, and Codacy. Apiary has a broader approval, being mentioned in 43 company stacks & 19 developers stacks; compared to ReadMe.io, which is listed in 33 company stacks and 4 developer stacks.
What is Apiary?
What is ReadMe.io?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Apiary?
Sign up to add, upvote and see more consMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
I cannot stress enough how important it is for companies to avoid Readme.io.
There is no accountability from their team when their service encounters serious errors. For weeks now, the service has been throwing internal server errors which were caught by monitoring tools.
In reaching out to readme.io support, the only information they ever gave was "Thank you" and a link to their status page. The status page does not reflect the fact the services is severely depredated and any further attempts over the past 14 days to reach support have been met with total silence.
Then there was an exchange with their CEO on Twitter who seemed like they may try to get us some sort of response or RFO, but that has also been met with silence after submitting exactly what was requested.
If you value the ability for your customers to reach your API Documents, then do not use readme.io.
README.IO DOES NOT CARE ABOUT YOU AS A CUSTOMER.
A pretty UI and the right combination of tools (tutorial section, API documentation, announcements) does not make up for consistently slow and buggy experience. As the amount of stored documentation grows, the app becomes more and more unreliable about saving changes, and for complex, in-depth documentation, the anchor tagging system is terrible, leading to false redirects. Multiple times, I have lost everything I've worked on, and the support service is terrible, even at the enterprise level. Other times, my changes are being saved, even though the app tells me they are not. I do not recommend this service for any company with lots of documentation.
Apiary é um excelente ferramente para documentação de sua API e guia para desenvolvimento do back-end. Utilizamos ele para garantir a informação correta a cada end-point.