Ihre Browserversion ist veraltet. Wir empfehlen, Ihren Browser auf die neueste Version zu aktualisieren.

Notes

Hello,

  • This is the first project of ours, especially for kids and seniors in mind, to ease their lives to remember important things of, or daily tasks. To emphasise this, each task gets an unique distinguishable random emoji assigned, which can be shown on even the smallest complication to remember it visually. So, please do not hesitate to point out the smallest deviations from a perfect product.
  • It is entirely in the latest swift/xcode programmed and needs no iphone to use (besides iOS 12+ installation yet, but it was already tested on iOS 13/ wOS6 for stand alone use - and will be immediately applied for when wOS6 officially released.
  • Of course for easy usage and to adapt to the user preference, all apple complications (on Gen.1 via Series 2 to  Series 4) are supported and tested on physical devices 11 in total (Series 1 to be tested after this beta application)
  • I intend to specialise on the apple watch series, and write especially for the two user-groups (kids and seniors), sometimes  switchable
  • for (general business use too) - like here [lila switch ⚙️] (to switch off some emojis kids prefer but probably unsuitable for business use or leave some out because of no fun factor for kids.
  • to be widely language independent, I used no textual controls, but only visual pictograms in form of selected easy distinguishable apple emojis.
  • I tried to help the user as much as possible via using automatic workflow methods, to easy apply limits - if hit, a warning (⚠️ with a number appears) it shows after acknowledge it, for example softly the oldest record for possibly best to delete to avoid user confusion and sudden stop, before adding an important new duty, or idea to remember.
  • There are about ten error messages (of course in emoji language to easy to understand by all) the workflow tries always to solve those problems by pressing the acknowledge buttons (no decision needed or required at that moment, the workflow provides always the best possible solution), sometimes  a “⚠️” to the record to see what was repaired, if possible.
  • for more advanced users a hard press is implemented on all screens, but to accomplish all functions hard press is not needed to be used.
  • To avoid the need of any explanations how the product works a simple workflow is applied. The app should be usable in any language without any translation, even kids w/o reading knowledge should be able to use it.

 I have also prepared some test data to ease the evaluations on sample views and maximal memory usage:

  1. Out of the box the max. count is limited to 8 records by 99 characters,  if you try to enter more then the max. records, an emoji alert message appears (⚠️00:) press [☑️] - then the workflow shows you to (maybe) delete the oldest record as suggested by pressing [] (or undelete  []) or even not to add anything - press green chevron [<] (or [< ] on older devices) to get back to main to see other oldest list of records to choose any others to delete. It is positioned to show the last 4 mostly best choices to delete.
  2. To test data in some international languages and see some displayed max. length text records and to test typical speeds and memory usage:  from the main page (????jigNOTES) press the right button ->[0/8⚙️],  you get page (⚙️) -> [long press], pick [x - Decline] to get to the (main page) again -> press there [0/8⚙️] to get to (⚙️) -> [long press] again pick [x- Decline] (screen moves up shows actual version and Build plus the support button with support@jignotes.com), -> long press again -> pick [x - Decline] to get to the mail page, there long press [pick Trash] - > you see a simulated read error alert (⚠️02:) - for simulated maybe repair () press [] then you see the (12/12) test records starting with "dictation saved ... „ ending with  <=99: 4 5 6 7 8 9 a ... 7 8 9“ showing the actual set truncation length of all records (here less then or equal 99).
  3. To fill up all records (max.12) to the maximal allowable sizes (á 99 characters) to see the max. memory usage and respective lowest reaction speeds, please follow this steps: (same like above in 2. , after you see the above 12/12 records, [long press] ->  [pick Trash] - > you see a simulated write error alert (⚠️03:) for simulated maybe repair press [] you see test records starting with randomised emojis (based under your selection of groups in ⚙️ - per default the switches 1-4 are all on and switched to games mode) and 99: 1 1 1 1 ... 2 2 2 2 ... up to 12 12 12 12 1 browsable records. 
  4. To reset to the standard 8/8 from 12/12 records [Deep press] pick [Trash] to delete max. Test data and follow the steps in 2. then delete the last 4 records, you should see the “green apple....“ as the last record and (8/12) press [8/12⚙️] then [Deep press] then [x - Decline]  then [8/12⚙️] then [x - Decline] (now is the chance to see last Startup in milliseconds see 5.) then [Deep press] you are back to main page and the count is back to normal (8/8) and normal test data.
  5. If you see a statement below shows up “Startup: 136 ms” i.e. on the apple watch 4 you will see some other values depends which watch you are using i.e. apple watch 0 (Gen.1) shows “Startup: 423 ms” also about half a second. I set the time with the first “struct var start = Date()” in ExtensionDelegate.swift and calculate the time difference “start.timeIntervalSince(Date()*1000” at the very end of “func awake” of the InterfaceController.swift  (difference to real startend “willActivate” as last statement is only 1ms) so I can measure some relative first start times by reloading the program via xcode Build and run to see Startups under different loads like 432ms for empty database same with max. filled (second test Data) database gets me to 1211ms on my apple watch 4 but under expected typical load (first Test Data) goes  down to 1028ms.
  6. Voice entry is truncated to 99 characters after a too long dictated entry (so far as I know there is no way to limit the dictated characters in advance to the dictation, besides limiting the time of the dictation - maybe time limit will be added later to avoid too much truncation and unnecessary long dictation for this App) at this time a warning (⚠️10:) appears showing that the dictation entry limit/time later was overrun (⌚️>⌛️...) 
  7. so good so far, hope it helps, please contact me if you have any questions, Thanks, Laszlo