Look for Single Page Apps to be a defining characteristic of API-first SaaS 2.0 companies.
What else? What are some more thoughts on API-first SaaS 2.0 Single Page Apps?
2 thoughts on “API-First SaaS 2.0 Single Page Apps”
In technology I think we’ve seen the pendulum between fat/thin clients swing back and forth several times. I think many companies are starting to realize the downsides of single page apps (fat clients) and have started to reconsider less complex clients (thin clients).
| And, these Single Page Apps work best against REST APIs, the same APIs that make a product API-first.
I’m starting to feel pretty strongly that “Public API first” has some pretty serious tradeoffs that companies fail to take into account before releasing a public api. Once a public api exists, it serves as a contract between you and your customers/prospects. Breaking that contract can inadvertently break customer/partner integrations which can result in upset customers. Maintaining legacy API contracts can significantly affect your products ability to scale/iterate/change with customer growth and needs.
I’m not saying don’t build a public api, but think carefully about the tradeoffs. Be very judicious about the information you expose, because your api contract is something you will likely be bound to for the life of your business