Q: Is submitting Quiz Results to Google available in the most current version of Lectora Inspire?
A: It has been there for quite some time. It is definitely part of Lectora 12 and 16. Technically, it is also available in Lectora 11 but unfortunately Google changed its submission API since. So courses built in Lectora 11 won’t be able to submit to Google Drive nowadays.
Here’s a good tutorial.
Q: So you must publish the Lectora file as an HTML zip file, right?
Q: Where does one install these files? On the phone?
A: You upload them to http://build.phonegap.com, which converts Lectora HTML output to a mobile app file. The app can be installed on a phone or submitted to App Store for distribution. Please note you will have to go through a few hoops like paying Apple $99 for a Developer license or generating a secret signing key to prove ownership of your apps. Luckily, all of this is well documented by both Apple and Google.
Q: When you say old Lectora vs new Lectora, what versions are you referring to? I have Lectora 11.3.2.
A: The “old” Lectora is the non-responsive one, i.e. version 12 and older. The “new” Lectora is the one with Responsive Course Design feature, i.e. 16 and newer.
Q: How long did the entire process take?
A: About two weeks to build everything, test and publish. But I had a lot of experience with Phonegap / Cordova from building the last year’s app, and my computer was already set up.
Also, plan another couple of days to download and setup Xcode (for iOS emulation, works on Mac only), Android Studio (for Android emulation, cross-platform) and Cordova (for publishing to your local phone over USB). Or you can skip the local setup and just use the Adobe Phonegap cloud but the publish-upload-test-fix-publish cycle takes time, too.
Also, Apple can take up to 9 days to review and approve your app, so plan for it accordingly. You can track current review queues here: http://appreviewtimes.com/
Q: Don’t you have problems with nexus phones? With the soft keys in the bottom? Are those overlapping the content?
A: Depending on the type of Android phone, the following behaviors are possible:
a) hardware buttons – full screen is available to the users
b) software buttons that are always visible (on older Androids) – they will “steal” some space off the bottom the screen so users will have to scroll up to see the bottom 20-30px of you page.
c) software buttons that auto-hide (on newer Androids) – full screen will be available to the users and they will have to swipe up from the bottom of the phone to see the buttons. The buttons will be semi-transparent and overlay the content. Here’s a picture of options B and C:
Q: Not a question. In order to test the ios devices you need provisioning profile on a apple account and connect the with phonegap.
Q: So to test on a real device, it needs to be submitted to the app store?
A: Testing procedure for iOS and Android are a bit different. Both require you to create a secret key to sign your apps with and upload the key to Phonegap. You only have to do this once. But with Android, you can create the key with one line of code on your PC. With Apple, things are quite a bit more cumbersome. First, you have to pay Apple $99 for registering as an iOS developer. Then, you have to get the UDID numbers of all the devices you want to test on and submit them to Apple. Then, you get your developer certificate from the Apple portal, convert it to a secret key and upload to Adobe Phonegap cloud.
Once you get both secret keys to the Adobe Phonegap cloud, you will be able to download the apps from it to your phone and test. No App Store is involved in this. You only need to submit to the app store if you want to distribute the ready app to the users.
Q: Time consumed : Lectora app vs hybrid app without Lectora?
A: Well it depends on how quick you can develop custom HTML code as compared to building it in Lectora. Converting the resulting HTML output to an app takes the same amount of time (that is, very little). For many people who already know Lectora, the investment into learning to build responsive HTML for mobile devices is really unnecessary since Lectora covers 99% of functionality needed for an e-learning app and outputs robust and tested code.
Q: (Various questions on sharing)
A: I’ve shared everything on the Community: http://community.trivantis.com/shared-content/luc-2016-app-assets/