attachment-0002
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>In reference to the mobile print clients discussed today, I think the following use cases need to be accommodated as well. Do my comments seem reasonable, or do they need more detail?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I also think there should be an attempt to have a standard call that results from the user’s desire to print – currently mobile devices can have a print button, or “share with”, or start the print app first, as just a few of the options. Not all printers are available for similar applications.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Larry<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Case 1.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>User is responsible for printing an odometer affidavit which must conform to the state’s legal requirements. The user starts an application on their mobile device which accepts the required input data, including odometer reading, VIN, Registration details, etc.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The user clicks on a print preview button that displays the data for printing. The user is not presented any print options due to the legal format restrictions, only the printer status. Print destination was determined by user location and/or ID.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Case 2.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>A financial service branch representative meets with a client to discuss a product. The client decides to purchase a product and needs to review and sign several printed documents. These forms are identified as controlled by a regulatory agency, and must be printed in a specific format. The advisor inputs the needed information on their mobile device and selects print preview. After review the advisor sends the data to a printer that has the appropriate capability, including any special forms or paper.<o:p></o:p></p><p class=MsoNormal><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div><br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body></html>