My two cents about software development on the web


BYOD is unstoppable. Smart companies must build apps

This is an old post but I think it’s still relevant.

The Bring Your Own Device (BYOD) movement has gained unstoppable momentum. And thanks to the burgeoning mobile app market, employees have high expectations for these tools. They want an attractive user experience tailored to their devices. In other words, companies need to invest in building apps, period.
During the internet explosion, applications settled on three tiers: presentation, logic and data. [..] the lines between the presentation and logic tiers frequently blurred, and a hard border was created between the logic and data tiers.
However, I believe that the overwhelming emphasis on user experience combined with the impact of cloud and big data will now blur the line between logic and data, and the border between presentation and logic will become much more complete. That concrete border has a name: it is the API. That order process now needs to be available on the web and to a variety of mobile devices, so that the logic tier can be accessible to all channels through the API.

source: BYOD is unstoppable. Smart companies must build apps — Tech News and Analysis.


Linkflood – About REST

This is my personal list of resources about principles and guidelines for designing RESTful Web APIs.


Lessons from the API giants

 Any company looking to utilize an API to expose its services – and every company should be looking at this – can stand on the shoulders of these giants:

  • Use your API as a new channel for your business like Salesforce
  • Align your API with your core value proposition like Amazon
  • Create a thriving community of developers that use your API like Twitter
  • Keep improving your API’s usability like Google

source: 5 lessons from API giants like Twitter and Google


Enterprise Needs for Enterprise APIs

Enterprises however, have to approach their API strategy differently than smaller companies.  For startups, getting recognition, traction and customers is most important.  Allowing as many people as possible to use their API makes the most sense

For enterprises, the goal is to increase internal efficiency as well as expand brand presence without diluting it. Their API strategy, therefore, has to be segmented.

To tailor an API strategy to their needs, large companies need to think about what data/services they can provide to all of their audiences, then segment accessibility of the API based on the audience.

However, the concept of determining who should have access to your API, depending on how important or sensitive your data is, is applicable to the majority of enterprises.

source: Enterprise Needs for Enterprise APIs


9 uses for cURL worth knowing

Working with HTTP from the command-line is a valuable skill for HTTP architects and API designers to have. The cURL library and curl command give you the ability to design a Request, put it on the pipe, and explore the Response. The downside to the power of curl is how much breadth its options cover. Running curl --help spits out 150 different flags and options. This article demonstrates nine basic, real-world applications of curl.

In this tutorial we’ll use the httpkit echo service as our end point. The echo server’s Response is a JSON representation of the HTTP request it receives.

source: 9 uses for cURL worth knowing | httpkit | Tools for hacking on HTTP.