<html 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=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=DE link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span lang=EN-US>Hi,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>I’ve been thinking about making Ezra Project available for Tablets, initially Android, later potentially also iOS.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>I realize that some people are simply not using a traditional desktop any longer. And with tablets you can even handle more involved tasks that make use of the bigger screen in a similar way as it is on desktops.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>My plan would be to keep the exact same user interface that is used for the Desktop version and make that available for Tablets based on minimal code changes. Note that smaller devices (Smartphones) would specifically be excluded from this plan, because the existing user interface certainly wouldn’t work on such small screens. However, on bigger screens it makes sense to re-use the existing UI.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Technology wise I’m considering Node.js for Mobile Apps, which is an enabler for this porting effort (in combination with Cordova):<br><a href="https://code.janeasystems.com/nodejs-mobile">https://code.janeasystems.com/nodejs-mobile</a><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Node.js for Mobile Apps allows to use a similar architecture as on the Desktop with Electron – nodejs running in a separate process/thread while communicating with the frontend via a message-based IPC interface.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Before moving forward with this idea I wanted to get some feedback.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Best regards,<br>Tobias<o:p></o:p></span></p></div></body></html>