The Costs to Expect API is approaching the point where it includes all the standard and expected features; you can add items, edit, list, delete and summarise the data, all the features you would expect at a minimum from a basic Rest API.
This summer, the fun begins, almost one year after development began I get to start work on the non-standard features and start developing the Costs to Expect service.
It took a long time to get here, well, a year. One year ago, I had an idea; now there is a Rest API, three web apps that use the API and a shiny new website showcasing five years of data that we have collected.
I know what we have planned for the next couple of months, and I know the long term goals, it is going to be interesting to look back again in 12 months to see how much progress there was and how much we still have to do.
I’ll blog more about the specific features when I start development, during the summer, I expect progress will slow slightly as I spend time with my family.
Costs to Expect API – https://api.costs-to-expect.com
Costs to Expect Website – https://www.costs-to-expect.com
Costs to Expect on GitHub – https://github.com/costs-to-expect