A brief navigation guide to the world of Android ROM manipulation
Android is the fastest growing OS for embedded devices that expect user interactions and cater to multimedia. A major reason for the steady adoption of Android is that it’s application framework works on top of a Linux kernel and has modest hardware expectations. In this blog I intend to pen my understanding of cooking up an Android ROM which is a fast way of creating a modified/custom version of Android OS image from an existing stable one.
A system on a chip is an integrated circuit that integrates all…
An advanced user’s guide to Go-Room
This is the last article in my series on Go-Room. I strongly recommend reading primer for Go-Room in practice and architecture deep dive of Go-Room as prerequisites. Go-Room is data store agnostic by design. If you are storing data on edge devices and would like to version control it’s schema, Go-Room can be an excellent choice. This article is intended to help developers channel their inner Ninja and plug Go-Room to any edge data store of their liking.
Delving into details of how go-room works
If you haven’t read my article on a primer for Go-Room in practice, I strongly recommend reading it as a prerequisite. In the primer, I discussed the primary intention of Go-Room which is to serve as a version management tool for edge data stores.
The charter for Go-Room is simple and short:
A version management utility for edge data stores
If you have written an application which runs on edge devices it is very likely that you used a data store. It could be to store user preferences, transaction logs or cached intelligence data for offline capabilities among many other such use cases. As developers focus on offline capabilities to address network issues and low bandwidth limits, data stores tend to be a crucial part of the application.
What’s next :)