Re:Why you absolutely MUST write an API when you write your ...
by wlievens on Tuesday November 23, 2010 @04:37AM
(#1933156)
I can second your question. When you build an app with a dynamic frontent (i.e. javascript) and a "database" (I don't care what model) driven backend, then you need a way to pass data and commands (e.g. JSON) between the two.
Thus you end up with pages that handle requests and return data in a structured presentation-agnostic fashion. Isn't that already an API?
An API, application programming interface, is an interface presented by some means into some kind of an application, possibly itself. A C library, for example, presents an API. Both external (public) and internal (private) APIs may exist, as well as intermediate forms.
An app, application, is a software program.
Here the advice is of a unified (public + private) web-based presumably RESTish API into a web application right from the start.
Contrary to the author's experience (or nomenclature), it seems to me that engineers typically do ensure their application has an API.