Lowest cost Android tablet as a component?

I bought one of those dinky CPC things -- Scroll 4" Android tablet -- the urge proved irresistible.  Such is the danger of sub-£30 pricing, random things get bought on a whim even without any projected use nor reason.

As it turns out, you get a lot for your money.  While it's not Gorilla glass nor metal, the unit is surprisingly solid, and even heavy for something this small.  Everything I've tried works fine on it, even the documentation is good (both paper enclosed and online product brief and manual), and I'm hard pressed to think of any real shortcomings at this price --- maybe battery life is on the short side (battery is 1400mAh).  For a little Cortex-A8 (A13), it's doing a great job.

Of course, a 4.3-inch screen is not my idea of "usable" for a tablet (YMMV, and Y<Eyesight>MV), but bearing in mind that this thread is not about Android tablets for normal use but about employing them as an HCI component for projects, the screen size can be entirely satisfactory or even on the large size.

I'll examine it further on rainy days.

This weeks CPC mail shot arrived with another cheap tablet http://cpc.farnell.com/goclever/r70kb/tablet-7-k-b-bundle-tab-r70-kb/dp/SB05246?Ntt=sb05246

it's a bit more than the 4" scroll, but still interesting

Unless you were offering your example of REST to Christy

sure, no problem.

It actually raises an interesting question as to how much room for change is available.  They regularly mention things that would require their vendor to fix or to develop, yet E14 has a development team (not just ops) so they must be developing something.  I wonder in what areas they are free to do so.

It actually raises an interesting question as to how much room for change is available.

The existing UI is based on REST, so infinitely customizable.

The underlying database not so much.

Oops, sorry, I missed a couple of  words essential to the question:

It actually raises an interesting question as to how much room for change is available to E14.

To the vendor, change is of course unrestricted, but that was not what I meant.

To the vendor, change is of course unrestricted, but that was not what I meant.

jive is the vendor. 

E14 or you or I can do whatever they want with the UI, including replacing it entirely,

which is where most of the concerns lie.

Judging by Dave's comment above, E14 either can't or don't want to replace the UI, nor even to modify it significantly.  That's why so frequently they tell us that they need to check with the vendor, even for bug fixes.  It seems that the bulk of the solution is bought in, otherwise they wouldn't be so dependent on what the vendor can do.

E14 either can't or don't want to replace the UI, nor even to modify it significantly. 

They "can", but they don't want to because it's a pain to merge their customizations

every time jive releases a new version, a typical open source problem.

To which open source has a strongly recommended solution, which is to push changes upstream.

To which open source has a strongly recommended solution, which is to push changes upstream.

That only works to the degree that upstream is receptive.

To which open source has a strongly recommended solution, which is to push changes upstream.

That only works to the degree that upstream is receptive.

Hopefully being paid by E14 makes them more receptive.