- * Launch time (first time and subsequent times)
- * Changing Bible translations (such as going from KJV to unencrypted WEB to encrypted version like NIV or NKJV)
- * Reference lookup, such as John 3:16 (should be very fast)
- * Simple one word searches (like how many times does “and” appear, or less common word like “jerusalem”
- * More complicated searches with multiple words like exact match of “meat eat” (should find 35 matches with KJV)
- * I have almost no experience with Android/iOS devices.
- * I've briefly watched people using them, and the devices seemed to have at least decent responsiveness.
IMO, if the performance of current mobile software is acceptable on iOS and/or Android devices, then it might be “re-inventing the wheel” and/or poor stewardship of time/effort for TW to be developed for ARM based devices. I could certainly understand Costas' lack of enthusiasm for "porting" TW to mobile devices.