There is a saying that goes like this, “Beauty is in the eye of the beholder”. It’s true. How many times have you bought something that you loved and shown it to a partner/friend/colleague etc and not gotten the response or reaction that you had expected? If you’re anything like me, it happens often. Well the same is true in software. Don’t worry, we’re not going to go in to the ins and outs of beautiful user interfaces. What I am actually talking about here is slightly different and that is… Software is really only beneficial to someone who has a problem that the software can solve. Would you agree? So by releasing software, your goal as a creator is to get it in to the hands of people who have a problem or challenge that your software obliterates. What problem is the WordPress REST API attempting to solve and for who? Let’s examine the WordPress REST API. There has been a lot of chatter recently on blogs and Twitter about the pros and cons of building out a full API spec supporting all of the WordPress features verse iteratively releasing the API as it is being developed. Until recently, I was firmly in the camp of iteratively releasing the API, but the more I think about it, the
Share This