I suppose "development target" might be more apt. The whole purpose is to be able to write software for other people with minimal messing about with the kindle to see that it works.
So, for example, if you had an inclination to write various pieces of software that turn a kindle into a wall mounted device, this would be the meat of your pipeline. I could write a home automation panel, then later, a weather display, etc. The prior work means I can push those things and make sure they function well before releasing them to the public.
It's needed because it wouldn't be easy to replicate the Kindle environment on a normal PC. It uses old custom kernels, a very limited subset of userspace utilities, has an unusual display, etc.
So, for example, if you had an inclination to write various pieces of software that turn a kindle into a wall mounted device, this would be the meat of your pipeline. I could write a home automation panel, then later, a weather display, etc. The prior work means I can push those things and make sure they function well before releasing them to the public.
It's needed because it wouldn't be easy to replicate the Kindle environment on a normal PC. It uses old custom kernels, a very limited subset of userspace utilities, has an unusual display, etc.