About

• Moe Amaya
• Founder Robotist

README

Software has eaten the world—particularly, APIs have consumed earth like a tasty amuse-bouche. The mission of Robotist is to serve as a guide into the proliferation of APIs: sourcing, evaluating, and recommending the best API for your use case.

With that goal in mind, we’re building an in-depth, highly-technical resource for engineering leaders to help make buying decisions. Software is ultimately a human process, so we talk to founders, customers, and technical teams to ensure we’re getting real-life feedback and even writing code ourselves!

Our goals

{goals: ["discovery", "evaluation", "de-risk"]}

The goals of Robotist are threefold: to enable discovery, to execute technical evaluation, and to de-risk expensive buying decisions.

• Enable discovery - By creating free, high-quality resources available to all, we hope to inspire everyone to explore API vendors that they may have never even heard of.
• Execute technical evaluation - By reading API documentation and writing code, we ensure we understand APIs strong enough to have an opinionated recommendation.
• De-risk buying decisions - By talking to founders and real-life users while also doing technical research ourselves, we offer a powerful due diligence tool to help leaders make an informed choice.

The Robotist Methodology

• Research - Starting with primary research, we develop a foundational understanding of the market, vendors, and end-customers.
• Expert recruitment - To properly vet APIs, we find experienced technical leaders who have ideally implemented more than one vendor API and can talk through pros and cons.
• Interviews - For expanding our real-world understanding, we talk to founders, customers, and end-users to gauge experience across all product surface areas.
• Code - While talking to users is helpful, getting our feet wet with real code helps solidify what we’ve heard from customers. A lot can change in software, so we make sure to analyze new API endpoints, documentation improvements, and overall developer experience.
• Writing - Informed by the previous research, we craft a recommendation by analyzing use cases and mapping to the ideal API vendor.
• Publish and editing - As the nature of software evolves, we revisit each recommendation at least yearly to ensure we are providing the latest context.