DZone
Integration Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Integration Zone > Allowing for Relationships Between API Developers at the App Level

Allowing for Relationships Between API Developers at the App Level

Managing the relationships between developers and allowing multiple users associated with an API application isn't something I have seen before.

Kin Lane user avatar by
Kin Lane
·
Nov. 06, 16 · Integration Zone · Opinion
Like (2)
Save
Tweet
2.23K Views

Join the DZone community and get the full member experience.

Join For Free

Managing developers' access to an API is part of API management 101. Managing the relationships between developers and allowing multiple users associated with an API application isn't something I have seen before. Slack just added the ability to add what they call app collaborators, allowing you add "any existing member of your Slack team as a Collaborator, including members and Guest Accounts."

The functionality felt a lot like the social aspects that made GitHub more attractive than just Git. When it comes to developing messaging apps and bots, I can see a social layer doing pretty well. "Once a Collaborator is added, they’ll receive a notification from Slackbot letting them know they now have access to your app." Smells like an opportunity for API management providers to bake into user management solution, and if you want to take it to the next level, add a Slack messaging layer as an option.

It's a small feature, but I think it is one of the things that made GitHub work. It could have a similar impact at the API management level, allowing for more engagement between users who are working together on API integration. I am going to add it as a building block for my API management research even if I haven't seen it elsewhere. It is something I'd like to see more of, and maybe if I plant the bug, more providers will implement.

API app dev

Published at DZone with permission of Kin Lane, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • JIT Compilation of SQL in NoSQL
  • How Low Code Demands More Creativity From Developers
  • What's the Difference Between Static Class vs. Singleton Patterns in C#?
  • ETL/ELT on Kubernetes With Airbyte

Comments

Integration Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo