Hi George,
On 10/20/2013 8:55 PM, George Neuner wrote:
> On Sat, 19 Oct 2013 22:32:08 -0700, Don Y <this@isnotme.com> wrote:
>
>>> There are number of Android tablets that can be booted from their SD
>>> slots. You still need to root a copy of the OS (for the drivers), but
>>> you can leave the tablet system intact and put your customized system
>>> on a card.
>>
>> That would (probably) be ideal (in terms of preserving the original
>> functionality of the devices). I've, instead, been willing to
>> "settle" for status as an "app" so users could freely switch between
>> "me" and the other uses for their device(s).
>>
>> The biggest problem with Android *tablets* is size and cost. They're
>> hardly "unobtrusive". And, putting AT LEAST one in each room can get
>> expensive, fast! E.g., we'd realistically need at least 10, here
>> (assuming the "fixed" displays are handled with my current approach).
>>
>> They're just too large to slip in a pocket and carry around with
>> you -- without being VERY conscious of their presence.
>
> There's already a 7in smartphone available from a Chinese vendor. I
> think that's far too unwieldy to put to your face [maybe they expect
> everyone uses a BT headset] but 7in, depending on form factor, I think
> is kind of the minimum size for a *general* use tablet.
Dunno. I'm not an "iPad"/tablet user (my Tablet PC's are ~14in diag).
But, I'm not looking for a "general use" format. Think, instead,
of something like a remote control. E.g., for a TV, it might
nominally give you controls for volume +-, channel +-, and mute.
(I suspect these are the most commonly used buttons on a TV remote)
If you wanted to do something else -- perhaps *pick* from a set of
predefined channels -- the screen would be redrawn to give you that
set of "channel selections". Or, one of several (prioritized?)
screens of selections. I.e., you are now concerned with picking
a channel so there is no need to waste real-estate on PIP controls,
forward/reverse program navigation, etc.
If you're listening to a music program, you might, instead, be
presented with volume +-, track +-, pause, etc. I.e., you are
always making selections from a relatively small, focused set
of options. In much the same way that you want menus to be
short instead of long lists of every conceivable action/command.
Selections vary with your current/recent actions, location,
preferences, etc. So, the system can exploit the limited
screen real estate to focus on just those -- requiring you
to do something *else* to bring up other possibilities.
E.g., if you're in the bathroom, chances are, you don't want
to adjust the irrigation criteria! So, if you happen to have
some overwhelming desire to do this (while sitting on The
Throne?), you will have to go fish for those controls. But,
once presented, they won't have to share the screen with
the controls for the surveillance system; or the HVAC system;
or...
>> The smaller option is Android based *phones*. But, those are equally
>> expensive and hard to justify *not* being used as PHONES!
>
> Even used, phones are more expensive than similarly sized tablets.
Makes sense. They have to do more (maintain the radio, camera, etc.).
And, I suspect there is some bias in pricing that relates to service
plans, etc. (if phones are *too* cheap, then a carrier has less of
a "hold" on the subscriber: "It's only a $20 phone. If my new carrier
requires me to buy a different model, I'm only walking away from $20!")
> There are a quite a few "mini" tablets with screens in the 4 to 5 inch
Ah, last time I checked, 7" was the bottom of the line. I suspect
for exactly the reason you originally cited: minimum size for
general use!
> range. I don't pay much attention to them, but a quick search on
> Google turned up a few 4GB with SD slot for under $80 (didn't check
> new or used). Still may be too steep if you require lots of them.
My preferred UI modality is earpiece and touchpad. I don't like
having to tie up two hands *and* two eyes to interact with
<something>. (I suspect most folks have memorized the locations
of the "important" buttons on their TV remotes -- so they can
use the remote with one hand and without taking their eyes off
the screen! The same should be true of *most* interfaces, IMO.)
But, I think most people are nervous in any interaction that doesn't
involve their eyes. Even if their eyes should be elsewhere (e.g.,
on the road ahead!). But, this can also be a deficiency in those
interfaces: lack of nonvisual feedback to confirm your actions
and/or an ability to easily "undo"/correct actions ("Crap! I
didn't want to change channels... I wanted to mute the audio!
Now I have to get the previous channel back *and* mute the audio!")
C grumbles at the thought of having something in the ear all day!
> Real question is whether you can shoehorn your app(s) onto the tiny
> screen, allowing for failing eyesight, shaking hands, etc., that you
> like to worry about.
It seems (empirically) that a handheld interface can be smaller
for a given set of "disabilities". I.e., a user can bring the display
to whatever focal distance is best for their eyes (assuming your arms
are long enough :>). ET/PT can be compensated by resting the
active hand on the edge of the handheld and extending an actuating
finger into the active surface. etc.
By contrast, a fixed display/interface (e.g., on a wall) seems like
it needs to be larger to get the same sort of "interaction reliability".
The wall won't move *with* your hand, etc.
> The form factor becomes more important with
> smaller screens: long and narrow is easier to carry or put in your
> pocket, but if the user needs to read much (not just identify icons),
> personally I think a more square form is easier to work with.
Interface is intended to be terse. Imagine how the exact same
interface is mapped onto an aural modality. "Lots of text"
read to the user would place a high cognitive load on him/her.
Instead, you'd opt for abbreviated representations.
"71 degrees cooling to 68" instead of "The HVAC system is set to
cool mode. The current setpoint temperature is 68 degrees but the
present indoor temperature is 71 degrees. As a result, the ACbrrr
is actively cooling the house at this time. The override is not
currently in effect."
"channel 13 at 28%, paused" instead of "The TV is currently tuned
to broadcast channel 13. The volume is at 28% and the program
material is currently paused"
[exaggerated text examples, of course]
All the extra words that might make a 3rd grade English teacher
happy are just extra clutter that the user has to wade through,
aurally.
[I believe "aural memory" is significantly different/shallower
than "visual memory". I.e., it seems like it takes more effort
to remember a long string of words received aurally than the
same information presented in a visual form. Though that may
just be a personal limitation? I've been exploring other
options to convey information aurally -- "sound icons" - in
the hope that you can remember a particular *sound* instead
of specific words. But, that "lexicon" quickly becomes yet
another cognitive challenge! :-/ ]