March 2022 Summaries

The integration of Java SDKs into Android applications is made possible through the use of low-code approaches that allow for easy communication with various APIs. APIMatic provides a developer experience platform that offers automatic code generation for API specifications in multiple languages, including Java. By utilizing client SDKs, developers can reduce manual coding and increase API adoption. The choice between using JAR or AAR files depends on the need to include resources such as layouts and drawables, with JAR being a better option due to its lightweight nature and compatibility with IDEs like Eclipse and Android Studio. Maven is used as the project management tool for APIMatic SDKs, allowing for easy integration into existing Java applications. Gradle's build system makes it easier to include external binaries and library modules, enabling developers to consume Maven libraries with ease. The Calculator SDK can be integrated into Android applications using either remote or local dependencies, with options available in Android Studio and through the use of Gradle settings files. Once the dependency is resolved, developers can easily use the SDK components in their application, as demonstrated by Java and Kotlin code samples.

The COVID-19 pandemic has led to an increase in the adoption of APIs, resulting in a rise in API specification documents. The design-first approach for building APIs has become more prevalent, leading to intriguing trends in API specifications. Postman Collections are the most popular input format, used by nearly 30,000 users over the past three years. OpenAPI v3.0 imports have surpassed v2.0 imports, but OpenAPI v2.0 exports remain high due to tool support and stability issues with newer versions. RAML is losing popularity, while API Blueprint is no longer actively maintained. WADL is best suited for XML APIs, but its usage is decreasing due to the rise of JSON-based formats. The top use-cases for API specification transformations include converting Postman Collections to OpenAPI, downgrading from OpenAPI v3.0 to v2.0, and migrating SOAP APIs to REST. Invalid API specifications are common, with unresolvable references, syntax issues, and mismatched component types being the most frequent causes. The API community is converging towards accepting OpenAPI as the standard for describing REST API services, while new technologies like GraphQL and gRPC emerge.

The Covid-19 pandemic had a significant impact on APIMatic's work environment, but the team adapted to remote work and continued to bond with each other. To celebrate their 6th anniversary, they organized a two-day event that included a speech by the founder, award ceremonies, customized gifts, and activities such as jet skiing, tug of war, volleyball, paddleboarding, parasailing, and Ziplining. The celebration also included a team-building lunch at Whispering Pines resort, where team members enjoyed stunning views and each other's company while working remotely. The event was a huge success and marked a return to normalcy for the team after two years of pandemic-induced isolation.

The APIMatic Kubernetes Operator simplifies the deployment of containerized applications, including APIs, in on-premise production environments by providing a straightforward setup process that cuts down deployment time to minutes, allowing users to get up and running with APIMatic quickly. The operator offers features such as deploying APIMatic CodeGen Web API service within a Kubernetes or OpenShift cluster, exposing the service externally, and manual horizontal scaling of pods. To deploy the operator, users need to meet certain requirements, including installing specific tools and software, and then follow a direct deployment process that involves cloning the repository, running commands, and creating necessary resources such as secrets and configmaps. Once deployed, users can access the exposed APIMatic CodeGen API service and generate API SDKs and Docs using various tools.