[Ongoing series of blog posts to
inform potential developers, users and (hopefully investors) about this new app
ecosystem I am architecting, designing, developing and deploying. More details
at this page]
I have written extensively about the design technique that I plan to follow to
build the API Engine. The API Engine itself is a collection of APIs. For the
last few days, I have been analysing the APIs that will make up the first batch
of contribution towards the engine. I noticed that there are some essential
tech components that they need to use to make it work.
Going by the design that I put in place, this is the second
bubble from the API design titled as ‘Identify all Tech’.
So, here is the full list of tech’s that are identified to
make this happen. The blog post image above lists it.
- Build and Deploy an API
- POST and GET to the API
- PUSH and PULL from the API to the Data Service
- Google Maps API on Android, Web and iOS
- Facebook Login API on Android, Web and iOS
I will of course, follow the design plan, and repo the above
stuff, tutorial it. After that (these steps will take a few weeks to complete),
I will finally have some serious unit testing to work upon.
As they say in the good books (mostly, there are no good
books that I refer to. It simply me using them as proxy :P), exciting times lie
Follow me on twitter, facebook and instagram for more