developerprogram.com - blog - “Yes, we enable the mobile world.” header

“Yes, we enable the mobile world.”

Last week, a few of our team members went to San Francisco to exhibit at the Mobile World Congress Americas conference. While there, I had countless conversations with other exhibitors and attendees. As is the case with most conferences, these conversations can be repetitive and exhausting. However, there are always a few that stand out, one of which inspired this post.

Let me set the stage for you – as a software as a service based platform successful in helping our clients enhance their offerings through developer and partner programs, we were invited to exhibit in the NEXTech segment of the hall.

According to MWC Americas, this portion of the exhibition features “forward-thinking companies and innovative technologies that have demonstrated incredible disruption across the mobile ecosystem.” Given the description, I anticipated being surrounded by technology that impacts “the way we interact, communicate, work, and play.”

You can imagine my shock when I came across booth after booth of phone cases, screen protectors, and somehow, even fidget spinners. Of course I recognize the value in these businesses (maybe not the fidget spinners…), but I hadn’t expected so many exhibitors to take the term “mobile world” so literally – a significant contrast to the MWC exhibit in Barcelona. In fact, one attendee even came to our booth and pointedly asked, “Why are you here? What value do you even add to the mobile world?”

My answer to this attendee is the basis for this post: “developerprogram.com enables the mobile world by providing software to our clients that allows them to optimally publish APIs and SDKs in a program-based environment that stimulates the engagement of developers and or partners.”

What does that mean “to optimally publish APIs and SDKs in a program-based environment”?

To start, let’s take a look at the goal of any modern API. Netflix lead API engineer Dan Jacobson says the goal is “to treat any presentation layer the same. So if you have multiple Web sites…both of those sites run off the same interaction model through the API. They’re just presentation layers, the same way as mobile app or Google TV…Users are going to consume new material in any way they want to, wherever, whenever, and your goal as a publisher is to make sure that you have a presentation layer that serves them wherever that is. And in doing so, the easiest way, the most effective way to date is to leverage APIs, and invites a little bit on having the right talent surrounding it.

Our ecosystem management software, dpEngine, allows our clients to get the technical documentation into the right hands by means of a developer or partner program to ensure that users can consume materials how they want – which by the way has a 56% chance of being on a mobile device. (Want to learn more about the difference between a developer program and a website that publishes API documentation? Check out this white paper: More Than A Website).

Why is it important to “stimulate the engagement of developers and or partners”?

As Jacobson mentions, it’s important to have the right talent surrounding your APIs. We challenge our clients to leverage developers and or partners. These stakeholders enhance our clients’ solutions and allow them to be consumed in the ways users desire. Stimulating their engagement in the developer and or partner program increases participation, attrition, and growth, all the while bolstering our clients’ offerings and their overall ability to succeed.

So yes, just as developers and partners add value to the mobile world, we do too by empowering said developers and partners through our clients’ developer and partner programs, ensuring that everything consumed via mobile is done so yielding the optimal experience.