Rob,
maybe I'm too pessimistic (realistic?), but if you're targeting
users within that category, your spec lacks "doesn't like reading
manuals or searching the web for answers" and "likes watching short
videos", so working on the manual with these users in mind is
futile.
My last App support: the App told the user it can't connect to the
server, he should verify the server address and vehicle ID. I sent
him the data he should use. He insisted in having entered exactly
that. After four or five mails I finally got him to send me this
"screenshot":
<glkolgejahicndjc.jpeg>
Many current users (even v2 users) I have supported fit into that
category, none of them would (could) read anything longer than a few
sentences. The manual introduction section is already too much for
them, they normally just jump into using the system and they
normally fail at things like entering a server name or password
correctly.
Of course we should generally try to further simplify the UIs, e.g.
provide a select option for the standard servers and an account
registration API.
But the manual IMO is meant for the capable / advanced user trying
to get specific jobs done with the system.
For the "low end" user target, a single (!) page "first setup" sheet
is needed, and a series of 3 minute feature introduction videos on
Youtube.
Regards,
Michael
Am 03.01.19 um 16:05 schrieb Robert
Sharpe (Electric Vehicle Consultant):
Hi Mark/All,
Sometime ago I did lots of obvious updates of the User
Manual to help readability, etc as a first stab.
Now doing a second stab, there is one thing that has come
to light and that is the definition of a user.
In order to check the documentation I need to know what the
user is capable of off. I appreciate that the definition of
user has probably changed over the development of the project
and the product has matured enough that it can be operated by
non-technical users opening up its usefulness.
Assuming that what were the original users would how fall
into the category of Developers, does the following draft
specification accurately reflect the minimum capabilities of a
current/future User?
User Definition
- a general household DIY capable person.
- can mount and plug things into the vehicle
- cant
- create connectors/leads
- modify the OVMS hardware
- don't know about internal or technical terms, such as
Nissan Leaf GIDs, WiFi SSID, etc
User Expectations
- the unit fully supports the listed features under all
reasonable conditions
- reliable in operation
- error messages are non-technical and help the user solve
the problem
- should be plug-n-play where possible, eg
- automatically detects vehicle type and year
- automatically detects battery capacity, etc
Please let me know if this is accurate or what
changes/clarifications need to be made.
Rob
_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev
--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26