The purpose of this tutorial is to show you how to use Firebase to build user presence tracking - https://goo.gl/VxMqpd
The purpose of this tutorial is to serve as a starting point for a real world React, Redux, and Firebase example. The starter project is on GitHub here - https://goo.gl/Mrfi6W
The purpose of this tutorial is to serve as a starting point for a real world React and Firebase example. The starter project is on GitHub here - https://goo.gl/A0KhEv
As an Android developer, I spend quite a bit of time integrating existing web services. I typically will find a URI for a web service, and then use a debug console to figure out what params I need to pass it,... Continue Reading →
Introduction The goal of this tutorial is to load publicly accessible profile and activity information from a Google+ user using the Java Google+ clientlibs. You will need to download the clientlibs for Apiary (infrastructure client library) and Google+ client library... Continue Reading →
Overall, the API is pretty straightforward to use, assuming that you are familiar with asynchronous processing in the first place. However, if you are not familiar with asynchronous processing, then this business of callbacks can be quite confusing and daunting. Additionally Tomcat 7 and Servlet API 3.0 make it easier to configure servlets using annotations. There are other cool features in 3.0 that I haven’t covered in this tutorial, like loading servlets programmatically.
When creating android applications, that are not trivial, it is important to keep in mind that android activities, widgets, and services have somewhat autonomous lifecycles that are controlled by the operating system itself. This is profound impacts on how you have to think about applications, since there will no longer something unified, but rather are a lot of different parts that are being orchestrated somewhat randomly. For example, applications process can be terminated anytime, or its activities can be terminated, or its services can be restarted. If you do not plan for such diversity in lifecycle states when building each widget service or activity, you will have a really tough time syncing them all up in the final application.
The best way to handle GPS is to use the “network” or “passive” provider first, and then fallback on “gps”, and depending on the task, switch between providers. This covers all cases, and provides a lowest common denominator service (in the worst case) and great service (in the best case).