🧩 SDKs should unlock real workflows, not just item reads.

With 1Password SDKs, integrations can now support:
🧰 Full vault management (CRUD + list)
🔐 User-authenticated SDK sessions
🚀 Batch actions for performance at scale

The result is a new class of integrations designed for enterprise operational workflows, where managing access matters as much as securing secrets.

👉 https://bit.ly/3Mj3QWo

#DeveloperTools #SDKs #IdentitySecurity #AccessManagement #1Password

Should I apply there?? 🤔🤔🤔🤔

https://adjoe.io/careers/open-positions/8091e129-8708-40de-851c-b83b4331af00/

> Our #AntiFraud Solutions team tackles one of #adtech’s biggest challenges: industry reports suggest 25% of global mobile ad spend is fraudulent. We’ve built sophisticated systems that actively prevent fraud from impacting our partners’ business.

> At the core of our solution are custom-built mobile #SDKs for #Android and #iOS, which analyze device integrity and detect modifications like Xposed frameworks, Magisk modules or #jailbroken devices. Our distributed cloud infrastructure powered by SQS and Kafka processes billions of daily events to flag suspicious behaviors in real time, while Go-based microservices deliver millisecond-level responses using DynamoDB as our database.

Senior Go Backend Developer (f/m/d) | adjoe

adjoe is a leading mobile ad platform developing cutting-edge advertising and monetization solutions that take its app partners’ business to the next level. Part of the applike group ecosystem, adjoe is home to an advanced tech stack, powerful financial backing from Bertelsmann, and a highly motivated workforce to be reckoned with.  Meet Your Team: Anti-Fraud Solutions Our Anti-Fraud Solutions team tackles one of adtech's biggest challenges: industry reports suggest 25% of global mobile ad spend is fraudulent. We've built sophisticated systems that actively prevent fraud from impacting our partners' business. At the core of our solution are custom-built mobile SDKs for Android and iOS, which analyze device integrity and detect modifications like Xposed frameworks, Magisk modules or jailbroken devices. Our distributed cloud infrastructure powered by SQS and Kafka processes billions of daily events to flag suspicious behaviors in real time, while Go-based microservices deliver millisecond-level responses using DynamoDB as our database. For developers interested in cheat prevention, this means working with cutting-edge...

adjoe

KeyboardKit's Black Friday 2025 deal gives you 50% off your first KeyboardKit Pro subscription payment. This deal is valid for all tiers, which means that you can save up to $2500 if you sign up for a yearly KeyboardKit Pro Gold subscription! There has never been a better time to go Pro - sign up today!

#blackfriday #software #sdks

https://keyboardkit.com/blog/2025/11/25/black-friday

Black Friday 2025

KeyboardKit’s Black Friday 2025 Deal gives you 50% off on your first KeyboardKit Pro purchase! This means that you can save 50% of an ent...

I just recently noticed that there are not many in-depth resources about SDK documentation for technical writers. I think this presentation provides a good "no frills" overview of the topic:

"SDK docs written by developers tend to be implementer oriented, not user oriented. That makes sense, since it's the implementers writing them. Unfortunately, this approach leads to some frustrating SDK reference manual experiences for users. The implementer-oriented doc writer tends to answer, "What is this built on?" As a user, I need docs that tell me, "What can I build with this?"

I provide examples of common SDK docs pitfalls, then present the approach that I used updating the SDK documentation that our developers had created. My goal was to give users of those docs a quick, enjoyable, user-oriented experience. To do so, I identified the likely use cases, or flows, of our product. I then grouped all entities (classes, functions, etc.) of the docs into these flows. For each flow, I arranged the entities in "flow order".

Having mapped out our codebase in this way, I was ready to begin adding content by following these principles:

1) In the leading lines, answer: what is this for? 2) Always link to the previous and next items in all flows and add "See Also" links. 3) Add a code example that demonstrates this entity's role in the flow. 4) Call out gotchas that are likely to get in the user's way when trying to use a flow."

https://www.writethedocs.org/videos/portland/2019/sdk-reference-manuals-a-flow-based-approach-chris-bush/

#TechnicalWriting #SoftwareDocumentation #SDKs #SDKDocumentation

SDK Reference Manuals: A flow-based approach

Write the Docs

SwiftPackageScripts 1.1 is out, with a new GitHub Actions workflow template for building closed-source XCFrameworks and dSYMs. This release also adds new parameters to other scripts.

#swift #spm #sdks

https://github.com/danielsaidi/SwiftPackageScripts

I'll be giving my talk "SDK Best Practices - Building a Great Developer Experience" at BuildStuff (@buildstuffconf) in Vilnius, Lithuania. This is a longer version than the one I gave at Swift Leeds, so I will have time to cover a lot more. I'm looking forward to it a lot - it's a great conference! See you there? ☺️

#Swift #SwiftUI #SDKs

A recording of my talk Best Practices in SDK Development" has been published by the amazing @SwiftLeeds team. I haven't watched it due to severe cringe-related issues, but if you're interested in building SDKs, you may find it interesting.

#swift #sdks

https://danielsaidi.com/talks/2025/10/08/best-practices-in-sdk-development

Best Practices in SDK Development

I gave this talk at Swift Leeds in October 2025, on best practices in SDK development, and how to create a great developer experience, bo...

Do you struggle with unsymbolicated, obscure crash reports from closed-source, 3rd party SDKs that you use in your app? If so, check out this blog post about how to add dSYMs from a closed-source SDK to your app, to get symbolicated crash reports that you can actually understand and act on.

#swift #sdks

https://danielsaidi.com/blog/2025/10/19/adding-dsyms-from-a-closed-source-sdk-to-your-app

Adding dSYMs from a closed-source Swift SDK to an app

If your app depends on a closed-source SDK, you may find that the crash reports don’t provide a full strack trace for the SDK. Let’s see ...

🎉 Breaking news: #Postgres has a "LISTEN/NOTIFY" feature that didn't quite make it as the life of the party! 🎈NewRecall.ai discovers that it doesn’t "scale," a shocking revelation akin to discovering water is wet 💧. Just another day in the thrilling world of #desktop #SDKs and #meeting #bots. 💤
https://www.recall.ai/blog/postgres-listen-notify-does-not-scale #LISTEN #NOTIFY #NewRecall #AI #scaling #issues #HackerNews #ngated
Postgres LISTEN/NOTIFY does not scale

Postgres LISTEN/NOTIFY can cause severe performance issues under high write concurrency due to a global lock during commit. Learn why it doesn't scale and how to avoid outages.

🤔 Ah, behold the 'MCP Specification,' a sprawling labyrinth of buzzwords and acronyms promising to revolutionize the world with yet another "open protocol" nobody asked for. 🚀 Did someone say "standardized way"? Because obviously, the tech world hasn't seen enough of those. 🙄 Expect all the excitement of a tax code, but with SDKs!
https://modelcontextprotocol.io/specification/2025-06-18 #MCPSpecification #openprotocol #techbuzzwords #SDKs #standardization #HackerNews #ngated
Specification - Model Context Protocol

Model Context Protocol