Pitney Bowes.

PB Software Blogs

The Benefits of Self-Service Simplicity for Commercial and Corporate Developers

by Lorena Hathaway | September 30, 2015 | No Comments

Mobile ApplicationsThe ability to test-drive an API before investing in one is crucial. After all, developers need to feel comfortable and confident with an API, to ensure that it meets their needs and works intuitively toward their goals, if they’re going to adopt it as part of their day-to-day. As any developer can tell you, having to fight with a cumbersome API stacked with multiple processes for what should be simple functions isn’t just counter-productive, it’s downright frustrating.

That’s where the new Pitney Bowes Developer Hub comes in. This self-service developer portal exposes a collection of information, communications and commerce services to help our customers enrich their applications, business processes and workflows. We want self-service simplicity to be a part of every stage of the customer journey, including Learn, Buy, Get, Use, Pay and Support.

We also pride our Developer Hub on its appeal to two kinds of developers: commercial and corporate developers.

Commercial Developers

The commercial developer aims to attract new business or create new customer experiences by enhancing his or her company’s existing product or solution, or by building an entirely new one. To that end, commercial developers spend the bulk of their time refining the product’s user interface and experience design, to ensure an intuitive and engaging experience.

The downside to this role? Commercial developers also end up spending too much time trying to polish the UI/UX of third-party APIs that they’re integrating into their company’s products. Or they spend too much of their time navigating through outdated or superfluous APIs, requiring them to create their own Product Health Dashboards and Reports to compensate for poor logging or usage data outputs.

Corporate Developers

Unlike the commercial developer, the corporate developer looks to build or enhance business workflow for more efficient process automation; i.e. a more internal, rather than external, consumer-facing, goal. But corporate developers end up running into a lot of the same headaches as their commercial counterparts with third-party APIs: antiquated products, superfluous documentation, multiple outlets for usage and transaction data (when only one is required or wanted), and altogether sinking in unnecessary amounts of time into working around cumbersome or difficult interfaces.

Test Drive Our New Developer Hub

Despite their different backgrounds and needs, commercial and corporate developers suffer from many of the same issues with problematic APIs, and both desire the same simpler, streamlined approach of well-documented and jargon-free APIs.

That’s what makes our Developer Hub such a valuable opportunity for both groups of developers – they may want different things out of their APIs, but need them to work in the same productive manner. And the only way to guarantee that is to try it for themselves first.

To try out our new self-service developer portal for yourself, please sign up for a free trial account.

Please observe our community guidelines when posting comments.

This blog is hosted by Pitney Bowes Inc. By using this blog you agree that you are solely responsible for any comment you post to the Blog and you agree to abide and be bound by the Pitney Bowes TERMS OF USE.

Please stay on topic. We may redirect certain submissions if they are better handled through another channel such as customer service. With regard to the content of any submissions you make through this Blog, you agree to remain solely responsible and agree to not submit materials that are unlawful, defamatory, abusive or obscene. You also agree that you will not submit anything to this Blog that violates any right of a third party, including copyright, trademark, privacy or other personal or proprietary rights.

Pitney Bowes reserves the right to terminate your ability to use and/or submit posts to this Blog. Pitney Bowes may not review all postings and is not responsible for comments posted on this Blog. Pitney Bowes nevertheless retains the right to not post, edit a posting or to remove any postings in its sole and absolute discretion.

Comments (none)

Post a Comment

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>