I've been working on the software wish list, so I haven't had a chance to
respond to all the great comments, questions, and suggestions. So, this
note covers a variety of topics: construction and modification, hardware
notions, and target users.
-r
# Construction and Modification
Obviously, we expect users to augment, configure, and modify the software.
However, even with through-hole components, construction and modification
(eg, soldering tiny components without creating "solder bridges") will be
challenging for a blind or visually impaired person. So, YMMV.
That said, there's no reason why we couldn't sell both kits and completely
assembled (turnkey) units, assuming that the economics make sense for each.
# Hardware Notions
I've searched for a convenient, economical way to include batteries in the
Perky hardware. To date, I haven't found any appealing solutions. So, my
current notion is to supply power via USB (eg, from a power bank and/or a
wall wart).
## Perky Pup
My design for the Perky Pup's production hardware is based on a two-layer
printed circuit board. The components (eg, buttons, RasPi Zero W, sockets)
will mounted on the top of the board.
The mechanical design is up for grabs. A minimal device might get by with a
protective plate on the bottom (where the component leads emerge). I'd mount
this plate via bolts and stand-offs, to allow modification, repair, etc. If
the buttons and sockets need more support, a top plate could be added.
## Perky Pro
The Perky Pro design is much the same, save that the computer (RasPi 3 Model
B) and most of the sockets sit underneath the circuit board. It might have
a solid case, with access holes and a bolted-on lid. There will be quite a
bit of free space in the case, allowing the addition of an Arduino, etc.
The Cherry MX (mechanical, tactile) keyboard buttons have a solid reputation
and several options for clickiness, etc. Also, they aren't all that large
or expensive. So, it might be nice to use them in the Pro.
## USB/MIDI Keyboard
The idea of using a USB/MIDI keyboard for non-musical input (eg, Perkins-
style Braille chording) is quite cool. Although arbitrary "chords" aren't
likely to sound very pleasant, it should be possible to disable the sound
or remap the keys in some euphonious manner.
Although Perky into a commercial USB/MIDI keyboard doesn't seem like a path
to the really portable and economical device I have in mind, I'd encourage
folks to experiment in this direction if they find it interesting. We'll
just have to be sure to define a very general keyboard abstraction...
# Target Users
Chris Moore asks about our target users:
First, what class of users are we targeting? I’m assuming Braille users
with speech rather than Braille output. In addition, if we’re gearing
it toward the totally blind, a screenless device would be appropriate.
... from the user perspective, do we want a Linux feel, or a system
which runs under Linux but feels less geeky. ...
Third, Self-voicing menus or a screen reader or perhaps a combination.