# API Design Published articles for API Design. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Why API design must account for consumer coupling DevFeed: [Why API design must account for consumer coupling]() Original publisher: [Read original article]() Author: Franco Fernando Published: 2026-09-18T07:42:00Z Content type: article Language: en Sources: [The Polymathic Engineer]() Topics: [API](), [Development]() Tags: [api](), [api-design](), [architecture](), [article](), [backend](), [coupling](), [refactor]() ### AI overview This article introduces API design through the problem of consumer coupling. It explains why published interfaces become difficult to change when internal and external consumers depend on them, and argues that APIs should be designed from the consumers' perspective. ### Source excerpt Coupling, not naming. First article on API design. ## How API Design Is Evolving for AI Agents, Security, Reliability, and Compliance DevFeed: [How API Design Is Evolving for AI Agents, Security, Reliability, and Compliance]() Original publisher: [Read original article]() Author: J Simpson Published: 2026-09-17T07:00:00Z Content type: article Language: en Sources: [Nordic APIs]() Topics: [API](), [Architecture & Design](), [Artificial Intelligence](), [reliability](), [Security]() Tags: [agents](), [ai-agents](), [api](), [api-architecture](), [api-as-a-product](), [api-design](), [api-discovery](), [api-security](), [architecture](), [authorization](), [blog](), [mcp](), [microservices](), [rate-limiting](), [reliability](), [security]() ### AI overview This article examines six ways API design is evolving as APIs serve AI agents and other machine consumers, with implications for security, reliability, and regulatory compliance. ### Source excerpt For over two decades, API design and architecture remained remarkably consistent. Perhaps it's the outsized influence of Roy Fielding's RESTful dissertation, but API designers have stuck to the principles of stateless architecture, resource-based endpoints, and HTTP commands to an impressive degree. That's all starting to change, now that we've radically recontextualized the way we use ... ## 10 Tips for Preparing APIs for Agentic Access DevFeed: [10 Tips for Preparing APIs for Agentic Access]() Original publisher: [Read original article]() Author: J Simpson Published: 2026-08-27T11:40:00Z Content type: article Language: en Sources: [Nordic APIs]() Topics: [Artificial Intelligence](), [observability](), [Security](), [Architecture & Design](), [Cloudflare]() Tags: [agentic](), [agentic-ai](), [ai](), [ai-agents](), [api-best-practices](), [api-design](), [api-discovery](), [api-documentation](), [api-monitoring](), [api-security](), [apis](), [artificial-intelligence](), [blog](), [json-schema](), [oauth](), [observability](), [openapi-specification](), [security](), [workflows]() ### AI overview Ten ways to prepare APIs for agentic access by improving discovery, security, observability, workflows, and predictable design for AI agents. ### Source excerpt In May 2026, Cloudflare released a new tool called isitagentready.com. It analyzes a URL for everything an agentic AI would need to interact with a site and then returns a score out of 100. Even better still, it breaks down its assessment by category, letting you know how your site performs for discoverability, accessibility from ... ## The HTTP QUERY Method and RFC 10008 DevFeed: [The HTTP QUERY Method and RFC 10008]() Original publisher: [Read original article]() Author: ratneshmaurya2311@gmail.com (Ratnesh Maurya) Published: 2026-07-03T00:00:00Z Content type: tutorial Language: en Sources: [Ratn Labs]() Topics: [HTTP](), [Query (disambiguation)]() Tags: [api-design](), [backend](), [examples](), [http](), [query](), [web-development](), [web-development-http-backend-api-design]() ### AI overview This tutorial explains the HTTP QUERY method described in RFC 10008, including why GET and POST may be insufficient for complex searches and how QUERY works through examples. ### Source excerpt HTTP finally has a QUERY method. Learn what RFC 10008 changes, why GET and POST fell short for complex searches, and how QUERY works -- with simple examples. ## Using bots to implement fixes from pull request review comments DevFeed: [Using bots to implement fixes from pull request review comments]() Original publisher: [Read original article]() Author: hi@swizec.com (Swizec Teller) Published: 2026-05-13T00:00:00Z Content type: opinion Language: en Sources: [Swizec Teller]() Topics: [Code review](), [Pull Request](), [Artificial Intelligence](), [engineering-culture]() Tags: [ai](), [api-design](), [code-review](), [code-reviews](), [knowledge-sharing](), [pull-requests]() ### AI overview The article argues that bots can implement fixes requested in pull request review comments, allowing developers to review the changes and merge them when appropriate. It presents this as useful for small fixes and notes that code owners may need to re-verify the result. ### Source excerpt You know what's better than a code review comment? A fix. ## Resource Names for Enterprise TypeScript Monorepos DevFeed: [Resource Names for Enterprise TypeScript Monorepos]() Original publisher: [Read original article]() Author: Robin Wieruch Published: 2026-03-30T06:50:46Z Content type: tutorial Language: en Sources: [Robin Wieruch]() Topics: [TypeScript](), [Code](), [Structured-data]() Tags: [api-design](), [code](), [consistency](), [enterprise](), [monorepo](), [monorepo-resource-id](), [resource-oriented-design-typescript](), [typescript](), [typescript-resource-names](), [utilities]() ### AI overview This tutorial explains how to standardize resource names in multi-service TypeScript monorepos. It presents hierarchical resource naming, based on the Google API Design Guide, as a shared convention that replaces ad hoc string interpolation and supports consistent encoding and decoding across services. ### Source excerpt How to bring consistency to multi-service TypeScript applications by treating resource names and resource types as first-class concepts with shared utilities ... ## Pagination at Scale: Why OFFSET and SKIP Will Eventually Break Your API DevFeed: [Pagination at Scale: Why OFFSET and SKIP Will Eventually Break Your API]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-03-17T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [API](), [Database](), [MongoDB]() Tags: [api](), [api-design](), [b-tree](), [cursor](), [database-performance](), [latency](), [mongodb](), [pagination](), [scalability](), [scale](), [sql]() ### AI overview This article explains why OFFSET and SKIP pagination become slower and more memory-intensive as page depth increases. It presents cursor-based, or keyset, pagination as an alternative that uses an indexed range seek and reads a fixed number of rows, keeping fetch cost largely constant with list depth. The trade-off is that cursor pagination does not provide reliable absolute page numbers. ### Source excerpt OFFSET does not seek. The engine fetches offset plus limit rows, sorts them, and discards the first N, so cost grows linearly with page depth. Cursor pagination passes the last seen key instead of a page number, letting the B+ tree seek in logarithmic time and read a fixed number of rows, which keeps latency flat at any depth. The price is losing absolute page numbers. ## Designing Resilient APIs: Failure-Handling Patterns for Distributed Systems DevFeed: [Designing Resilient APIs: Failure-Handling Patterns for Distributed Systems]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-03-16T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [distributed-systems](), [Resilience](), [API](), [Architecture & Design]() Tags: [api-design](), [apis](), [async](), [distributed-systems](), [fault-tolerance](), [idempotency](), [jitter](), [observability](), [outages](), [reliability](), [resilience](), [retries](), [systems]() ### AI overview A practical guide to designing resilient APIs in distributed systems. It covers fail-fast validation, graceful degradation, idempotency for safe retries, and bounded retry policies using exponential backoff, jitter, attempt limits, and total time budgets. ### Source excerpt Resilience is failing in controlled ways rather than not failing. Validate and fail fast at the boundary, degrade gracefully by serving cached or reduced responses, require an idempotency key for side-effecting operations, and bound retries with exponential backoff, jitter, an attempt cap, and a total time budget. Unbounded retries amplify outages. ## Transitioning from REST to gRPC: System Design and Tradeoffs DevFeed: [Transitioning from REST to gRPC: System Design and Tradeoffs]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-03-16T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [gRPC](), [Remote Procedure Call (RPC)](), [Code](), [HTTP](), [JSON]() Tags: [api-design](), [client](), [grpc](), [http](), [json](), [microservices](), [protobuf](), [rest](), [rpc](), [schema](), [server](), [system-design]() ### AI overview This tutorial explains how gRPC uses .proto service definitions and Protocol Buffers to generate typed client and server code, serialize messages, and communicate over HTTP/2. It compares gRPC with REST and recommends gRPC for internal service-to-service calls needing low latency, schema-first contracts, or streaming, while retaining REST with JSON at the edge for browsers and external consumers. ### Source excerpt gRPC defines services in a .proto file, compiles them into typed client and server code, and transports binary protobuf over HTTP/2. Choose it for internal service-to-service calls that need low latency, schema-first contracts, or streaming, and keep REST with JSON at the edge where browsers and external consumers live. ## From Syntax Checker to Critical Reviewer: How We Convinced AI to Catch Real API Quality Issues DevFeed: [From Syntax Checker to Critical Reviewer: How We Convinced AI to Catch Real API Quality Issues]() Original publisher: [Read original article]() Author: Wix Engineering Published: 2026-01-07T10:09:21Z Content type: opinion Language: en Sources: [Wix Engineering]() Topics: [API](), [Artificial Intelligence](), [Developer experience](), [Usability]() Tags: [ai](), [api](), [api-design](), [developer-experience](), [mental-models](), [technical](), [usability]() ### AI overview The article examines how an AI tool reviewing API designs focused on measurable issues such as naming, formatting, and typos while missing developer-experience problems involving workflows, hidden rules, mental models, and usability. It describes this as a recurring bias and explains how the tool was adjusted to produce more critical reviews. ### Source excerpt Building an AI tool to review API design taught us something fundamental about how AI approaches quality: it confidently optimizes for the least important parts. Instead of flagging the quality issues that actually hurt developers, like confusing workflows, hidden rules, or inconsistent mental models, it focused on the safe, measurable stuff: naming patterns, formatting mistakes, even typos. Developer experience issues just didn't get caught, even though in our case, we specifically asked for... ## XML Modelling in OpenAPI 3.2: A Quiet but Important Upgrade for Enterprise Teams DevFeed: [XML Modelling in OpenAPI 3.2: A Quiet but Important Upgrade for Enterprise Teams]() Original publisher: [Read original article]() Author: Zaid Daba'een Published: 2025-11-14T14:54:07Z Content type: tutorial Language: en Sources: [DeveloperHub.io]() Topics: [OpenAPI Specification](), [XML](), [upgrade](), [API]() Tags: [api-design](), [engineering](), [enterprise](), [openapi](), [upgrade](), [xml]() ### AI overview OpenAPI 3.2 expands XML modelling with clearer support for namespaces, attributes, mixed content, and precisely named nested wrappers. The article explains how these capabilities address limitations in OpenAPI 3.1 and reduce reliance on parallel XSDs, proprietary extensions, and prose documentation. ### Source excerpt OpenAPI 3.2 modernises XML support with richer modelling, proper attribute handling, and nested structures. It removes old workarounds and gives enterprise teams clearer, more accurate ways to define their XML based APIs. ## Structured Tags in OpenAPI 3.2: Organising APIs the Way They Deserve DevFeed: [Structured Tags in OpenAPI 3.2: Organising APIs the Way They Deserve]() Original publisher: [Read original article]() Author: Zaid Daba'een Published: 2025-10-26T21:00:37Z Content type: article Language: en Sources: [DeveloperHub.io]() Topics: [OpenAPI Specification](), [Documentation](), [API](), [SDKs]() Tags: [api-design](), [api-documentation](), [engineering](), [modular](), [navigation](), [openapi](), [sdks](), [structured]() ### AI overview OpenAPI 3.2 adds structured, hierarchical tags that let APIs organize endpoints into nested categories. The article explains how this can improve documentation navigation, SDK organization, and maintainability for large or modular APIs. ### Source excerpt OpenAPI 3.2 introduces structured tags, allowing APIs to organize endpoints into nested categories for clearer, more maintainable documentation. ## Turning Hypermedia APIs into MCPs DevFeed: [Turning Hypermedia APIs into MCPs]() Original publisher: [Read original article]() Author: Daniel Doubrovkine (dblock@dblock.org) Published: 2025-09-18T09:00:00Z Content type: tutorial Language: en Sources: [Daniel Doubrovkine]() Topics: [API](), [Model Context Protocol (MCP)](), [MCP Server](), [REST API](), [Ruby](), [Open Source](), [Slack]() Tags: [ai](), [api-design](), [apis](), [hypermedia](), [mcp](), [mcp-server](), [mcps](), [model-context-protocol](), [open-source](), [rest](), [rest-api](), [ruby](), [slack]() ### AI overview This tutorial shows how to expose a Hypermedia API as an MCP server using the Ruby gem hyperclient-mcp. It uses the open-source S'Up Slack bot to demonstrate resource discovery, starting the server, connecting it to Claude, and querying bot and team information. ### Source excerpt I've written and talked extensively about Hypermedia APIs for about a decade. The HATEOAS constraints in representing resources for a RESTful API has numerous advantages in API design, readability, discoverability, and performance over a hand-rolled REST API. Unfortunately, adoption of Hypermedia APIs is very low compared to, for example GraphQL, but I find the implementation a lot simpler and continue adding Hypermedia APIs to my pet projects. At its root a Hypermedia API looks like so. { "_links": { "self": { "href": "https://sup2.playplay.io/api" }, "status": { "href": "https://sup2.playplay.io/api/status" }, "team": { "href": "https://sup2.playplay.io/api/teams/{id}", "templated": true }, ... } } The above example is an extract from this API. For this post we will use one of my Slack bots called S'Up, which generates fresh triads of team members in Slack to meet for coffee every week in an informal standup. The bot is open-source and you can try it here. Because the Hypermedia API structure is fixed with only "resources" and "links" (and similar to API frameworks such as GraphQL) you don't need an application-specific client to interact with the API. In Ruby, the most popular generic Hypermedia client is Hyperclient. With the API above, a client can retrieve the bot status, and using an API token obtained from an existing installation some team information. api = Hyperclient.new('https://sup2.playplay.io/api') do |client| client.headers['X-Access-Token'] = ENV.fetch('TOKEN', nil) end status = api.status puts "Bot is #{status.ping['presence']['presence']}." team = api.team(id: '1234') puts "Team name is '#{team.name}'." This will output "Bot is online." and "Team name is 'dblock'." for my installation. In this case, the generic client knew nothing about "team" - it was discovered programmatically and was, in a way, self-documenting. Unsurprisingly, this idea of templated resources is reused almost exactly the same way in the model context protocol (MCP). Therefor ## Ep. 2: Elevating Software Design in Go: Package Architecture in Modern Development DevFeed: [Ep. 2: Elevating Software Design in Go: Package Architecture in Modern Development]() Original publisher: [Read original article]() Published: 2024-05-21T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [Software Engineering](), [Architecture & Design](), [Code]() Tags: [api-design](), [code-modularity](), [dependencies](), [go](), [go-development](), [go-projects](), [integrity](), [modularity](), [package-architecture](), [scalability](), [software-design]() ### AI overview This video episode explains package architecture in Go. It emphasizes clear boundaries between components, focused package functionality, avoiding generic packages such as "Utils" or "Common," and the role of robust type systems in maintainable software. ### Source excerpt Introduction: In this insightful episode, Bill dives deep into the realm of package design, shedding light on its crucial role in software development. Here are three key takeaways for Go developers: Code Modularity: Learn how Go's packaging system creates essential firewalls between program components, enhancing maintainability. Focused Functionality: Discover the importance of designing packages that provide specific functionality, fostering code clarity. Avoiding Pitfalls: Bill warns against common package design mistakes like centralized "common" packages, promoting a layered approach to maintainable code. ## Diagrams and API design with AI DevFeed: [Diagrams and API design with AI]() Original publisher: [Read original article]() Author: Mike Published: 2023-06-14T03:37:00Z Content type: tutorial Language: en Sources: [Dev Details]() Topics: [coding](), [OpenAPI Specification](), [Artificial Intelligence](), [ChatGPT](), [plantuml]() Tags: [ai](), [api-design](), [best-practices](), [coding](), [example](), [openapi](), [plantuml]() ### AI overview Part 3 of a practical series demonstrates using ChatGPT to visualize a URL shortening service design with a PlantUML sequence diagram and generate an OpenAPI specification. It compares ChatGPT 3.5 and ChatGPT 4 for these tasks and explains how an API-first specification supports parallel UI and server development. ### Source excerpt Part 3 of a practical example of using AI for coding ## Google Accompanist: Experimental Jetpack Compose Libraries for API Feedback DevFeed: [Google Accompanist: Experimental Jetpack Compose Libraries for API Feedback]() Original publisher: [Read original article]() Author: Alex Styl Published: 2023-04-06T00:00:00Z Content type: article Language: en Sources: [Composables - Concise, no-fluff video tutorials for Android developers]() Topics: [Jetpack Compose](), [Google](), [Library](), [API](), [Open Source]() Tags: [api-design](), [compose](), [google](), [jetpack-compose](), [libraries](), [open-source]() ### AI overview Google Accompanist is an open-source collection of Jetpack Compose libraries used to trial new APIs and gather developer feedback. Libraries may later move into the official Jetpack Compose dependency when their APIs mature. ### Source excerpt Google's secret test lab for all things Compose ## A Brief Overview over the Most Common jOOQ Types DevFeed: [A Brief Overview over the Most Common jOOQ Types]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-09-06T12:30:37Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [SQL](), [API](), [Databases](), [Structured-data]() Tags: [api](), [api-design](), [cheat-sheet](), [configuration](), [context](), [dependency-injection](), [dsl](), [jdbc](), [jooq](), [jooq-3-17](), [jooq-in-use](), [logging](), [overview](), [queryparts](), [r2dbc](), [sql](), [syntax](), [type-system](), [types]() ### AI overview This tutorial provides a cheat sheet of the most important types in the jOOQ API, covering configuration, scopes, settings, and DSL APIs. It notes that jOOQ 3.17 includes more than 160 settings and explains how several type groups support query construction, execution, lifecycle management, and dependency injection. ### Source excerpt For new users working with jOOQ for the first time, the number of types in the jOOQ API can be overwhelming. The SQL language doesn't have many such "visible" types, although if you think about SQL the way jOOQ does, then they're there just the same, but hidden from users via an English style syntax. ... Continue reading A Brief Overview over the Most Common jOOQ Types -> ## Rolling out Roles DevFeed: [Rolling out Roles]() Original publisher: [Read original article]() Author: Isaac Seymour Published: 2022-03-11T00:00:00Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [Authorization](), [Authentication](), [API](), [Front end](), [incident]() Tags: [api](), [api-design](), [authentication](), [frontend](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [outage](), [post-mortem](), [slack](), [slack-incident]() ### AI overview The article explains how incident.io introduced user roles and permission scopes to support private incidents and future permission levels. It describes using fixed customer-facing roles backed by granular scopes, centralized authorization checks in APIs, and type-safe scope handling in the frontend through a generated client. ### Source excerpt Take a peek behind the scenes at how we built user roles into our product, and rolled them out to our existing users ## Migrating Your Design System to Jetpack Compose: Part 2 DevFeed: [Migrating Your Design System to Jetpack Compose: Part 2]() Original publisher: [Read original article]() Published: 2020-12-07T07:38:38Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Design system](), [Jetpack Compose](), [Compose](), [Library](), [API]() Tags: [algorithms](), [android](), [api](), [api-design](), [blog](), [career](), [component](), [compose](), [design](), [design-system](), [development](), [engineering](), [finance](), [functional](), [growth](), [implementation](), [java](), [jetpack](), [jetpack-compose](), [kotlin](), [legacy](), [library](), [money](), [opinions](), [software](), [startups](), [techniques](), [thoughts](), [training](), [tutorial](), [typography]() ### AI overview Part two of a series on migrating a design system to Jetpack Compose, covering custom theming, integration with existing APIs, risks from a rapidly changing library, and API design considerations. ### Source excerpt Welcome back to the second article in my series about migrating design systems to Jetpack Compose, where I talk about our experiences at Cuvva and how you can apply what we learnt to your team. In part one, I talked about planning ahead, modularisation and getting your team onboard. In part two, I'll talk about custom theming, about building ontop of existing APIs, how to minimise risk from relying on a rapidly changing library and pose a question about API design. ## Kotlin Multiplatform Mobile: Launching & Maintaining an Open Source Library - Touchlab DevFeed: [Kotlin Multiplatform Mobile: Launching & Maintaining an Open Source Library - Touchlab]() Original publisher: [Read original article]() Published: 2020-10-08T18:28:34Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [kotlin multiplatform mobile](), [Library](), [Open Source](), [Mobile]() Tags: [api-design](), [community](), [kotlin-multiplatform](), [kotlin-multiplatform-mobile](), [library](), [mobile](), [multiplatform](), [open-source](), [touchlabshare]() ### AI overview A Touchlab community discussion features engineer Russell Wolf explaining how he created and maintains Multiplatform Settings, an open-source library for Kotlin Multiplatform Mobile. He discusses its career impact, community feedback, roadmap, and code and API design decisions. ### Source excerpt Russell is a multiplatform engineer at Touchlab. He tells the story of how he decided to develop an open-source library for Kotlin Multiplatform Mobile. ## Kotlin and Exceptions DevFeed: [Kotlin and Exceptions]() Original publisher: [Read original article]() Author: Roman Elizarov Published: 2020-06-10T08:18:06Z Content type: article Language: en Sources: [Stories by Roman Elizarov on Medium]() Topics: [Exception](), [Kotlin](), [Java](), [Error Handling](), [Code]() Tags: [api-design](), [code](), [error-handling](), [exception-handling](), [exceptions](), [java](), [kotlin](), [programming]() ### AI overview The article examines Kotlin exceptions by tracing their origins to Java checked exceptions. It explains how checked exceptions were intended to reduce missed error checks, then discusses problems including boilerplate, overly broad API declarations, ignored exceptions, and poor compatibility with Java 8 lambdas and streams. ### Source excerpt Photo by John Mark Arnold on Unsplash What are Kotlin Exceptions and how should you use them? To figure it out let's look at their origins first. Exceptions came to Kotlin from Java. The story with exceptions in Java is complicated, though. I'll give a brief overview. The Origin Java has a unique concept of checked exceptions that were designed to solve the problem of verbose and error-prone error-handling (pun intended). In languages predating Java, like in venerable C, you have to write code like shown in this snippet when doing basic input/output: file = fopen("file.txt", "r"); if (file == NULL) { // handle error & return } // work with file, check for error after each file operation Every time you perform an operation that might fail due to some external circumstance, which happens especially often with files and network, you have to write code that checks the corresponding error condition and handles it. That's tedious, easy to forget, hard to debug. Java set on a noble goal to eliminate this problem. The solution was to use checked exceptions. Every file I/O operation is declared as throws IOException in Java and the compiler checks that you either handle it or declare that you rethrow it. The beauty of this is that you can write exception-handling code once for a whole bunch of I/O operations and you cannot forget writing it since the Java compiler is there to help you. file = FileInputStream("file.txt"); // throws IOException No error-handling boilerplate, no more missed error checks. It was such a bliss to program in Java... for a while. Problems Problems with checked exceptions accumulated over the years. Memory input/output APIs like ByteArrayInputStream were still declared to throw IOException that you had to handle even though it never happened, people abused checked exceptions in API design leading to long, contagious lists of thrown exceptions, developers routinely caught and ignored checked exceptions just to fit some exception-throwing API under an in ## The Dog Riddle DevFeed: [The Dog Riddle]() Original publisher: [Read original article]() Author: Márton Braun Published: 2019-04-25T18:00:00Z Content type: article Language: en Sources: [zsmb.co]() Topics: [Kotlin](), [API](), [Code]() Tags: [android](), [api](), [api-design](), [code](), [kotlin](), [marton-braun](), [sealed](), [sealed-class](), [zsmb](), [zsmb-co](), [zsmb13](), [zsmbco]() ### AI overview A Kotlin API design challenge asks readers to model cats and dogs, including dogs with optional breeds, while enforcing valid syntax and predictable instance creation. The article discusses submitted solutions, a common singleton-related pitfall, sealed hierarchies, and exhaustive expressions. ### Source excerpt A fun little challenge in Kotlin API design. Give it a try! ## Kotlin Delegated Properties for Designing a Simple Android Library API DevFeed: [Kotlin Delegated Properties for Designing a Simple Android Library API]() Original publisher: [Read original article]() Author: Márton Braun Published: 2019-04-11T19:00:00Z Content type: tutorial Language: en Sources: [zsmb.co]() Topics: [API](), [Kotlin](), [Library](), [implementation](), [Android](), [properties](), [factory function]() Tags: [android](), [api](), [api-design](), [delegates](), [factory-function](), [implementation](), [kotlin](), [library](), [properties]() ### AI overview This tutorial explains API design choices in the Krate Android SharedPreferences wrapper. It shows how Kotlin delegated properties can encapsulate reusable logic, persist values across application restarts, and hide concrete implementations behind a simple interface and factory function. ### Source excerpt When developing a library, designing an easy to use API while hiding unnecessary implementation details from clients is fundamental. Let's look at some API design choices we've made for our library Krate, an Android SharedPreferences wrapper. ## Optimized for Change DevFeed: [Optimized for Change]() Original publisher: [Read original article]() Published: 2018-12-12T00:00:00Z Content type: opinion Language: en Sources: [Dan Abramov]() Topics: [API](), [Requirements]() Tags: [api-design](), [apis](), [change](), [code](), [developer](), [optimized]() ### AI overview The article argues that good API design must account not only for readability, correctness, and performance, but also for how API consumers' code will evolve. It calls this "second order" API design and says APIs should accommodate changes such as moving, renaming, generalizing, optimizing, and fixing code. ### Source excerpt What makes a great API? [Next page]()