From Gomo Wiki

Revision as of 12:46, 6 February 2012 by Epicadmin (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


Frequently asked questions about GoMo

What skills do I need to use GoMo?

You only need basic computer knowledge. If you use programmes like MS Word or PowerPoint, then you will be able to use GoMo with no problems. It has an easy to use and intuitive interface.

Can I see a GoMo demo?

Indeed you can! We can arrange a WebEx session to show GoMo in action or alternatively we can come and consult with you to see how GoMo Learning can fit in with your wider L&D strategy.

What would the demo involve?

A demo takes about 30 minutes, providing an overview of the system, how to build an app and some examples of completed apps, showing how they translate from the build-screen to final deliverable.

Can I try before I buy?

Of course. Once we have established what your drivers are for using GoMo, we can set up a 30-day trial for you.

Can I build my own templates?

As all mobile apps follow a relatively rigid template that users are familiar with, GoMo doesn’t have diverse templating in this manner. However, this means you you simply place assets onto a page and then GoMo will lay them out for you. There’s a degree of customisation for the higher-resolution devices (e.g. iPads and other Tablet devices) where you can choose to divide content into two columns, but this is as far as standard template customisation goes.

If I build my own skins who owns the intellectual property?

If you build your own skins (look-and-feel) in-house, then any images you have created are your intellectual property. Another option is to commission Epic to develop new skins for you – if you are rolling out large amounts of m-learning but have no graphics capability in-house, we would be happy to advise on the various options for developing bespoke skins.

How can I be sure my mobile learning will work correctly?

Any GoMo apps you create can be reviewed on the device you are intending to deliver on. If it works at this stage you can guarantee it will work when you publish.

Can I review the app via the GoMo portal?

At present you can’t preview the app on the GoMo site, but this functionality is currently being developed. Although the on-site review will be in HTML5 – allowing you to review your project as a Web app, the best way to review the app is directly on the device that you plan to publish to as an online review will never be as accurate as it will be on the device itself.

How do I update content?

To update content you just need to log in to the web portal as you would to build the app. As long as you’re an administrator, project administrator or editor, you can update content easily, by selecting the appropriate project and making your changes directly into the editing screen.

Once I’ve updated content do I have to pay for it to be re-published?

Each pricing package comes with a number of free publishes. However, once you have used your quota, there is an additional fee to publish new apps or updates, so we recommend you carry out a close review before initially publishing the app to avoid hidden costs to amend errors. We also recommend only republishing when amends are crucial to the underlying learning.

Can I convert from PowerPoint?

Not at present. The file format and layout in PowerPoint are not compatible with GoMo. However, transferring content from a PowerPoint is as simple as cutting and pasting graphics and text from the presentation directly into the tool.

Can I review the same content in different formats before it’s published?

Yes. When you create something on GoMo it creates a set of assets that are saved to a project folder. We have a number of preview apps, including Apple, Android and BlackBerry so not only will you soon be able to review it in the portal but you can access the app on the device itself e.g. iPhone, iPad, Android Tablet and so on.

How does the version control work when multiple users are reviewing at the same time?

Unfortunately there is currently no version control and you will need to ensure only one person is editing content at a time in order to prevent users overwriting each other’s work. However, as an administrator you can easily implement different permissions for different levels of users, and from a review perspective there is no limitation to the number of people who can access the m-learning.

Is there some kind of locking mechanism to prevent people overwriting each other?

Not at this moment in time. However, one of the future developments we intend to carry out is a version control model which will not only lock the project to other users when an administrator is editing, but every time someone saves the project it will create a back-up copy so that if errors occur you can roll back to that user/date. (Hopefully available around January 2012)

Is there an issue reporting function within the tool?

Bug tracking is not built into the tool – this has been done intentionally as we have our own bug database at Epic. Future developments could include bug tracking to integrate with a client’s own bug-tracking database – however, this would require some research to determine which bug database is best suited to the client.

We have devices with different screen sizes, will all of the users have the same experience?

The user experience is very similar on different devices, but it won’t be exactly the same for every device as each has different input methods and capabilities. For example, many BlackBerry devices have a roller ball rather than a touch screen, so although the basic interactions remain the same, the navigation depends on the device. The resolution is often different on a BlackBerry too, and different hardware will effect the presentation of the final m-learning in subtle ways.

Tablets have a good deal more real estate, so if you choose you can have the main menus and sub-menus down one side on a persistent basis. However, as the content itself remains the same users will essentially have the same end-experience across multiple different platforms.

Technically, how does GoMo deal with different formats?

GoMo has a number of different device players, which format the same content to work on different platforms. The portal produces a set of assets including .png graphics files, .xml content files and mpeg4 video files, but treats this content slightly differently depending on which platform the app is published to. This means GoMo will take into account different resolutions, different hardware etc. for different devices. We currently support players for the following: iPhone, iPad, iPod, Android devices, BlackBerry and also HMTL5 Web apps.

Whos here now:   Members 0   Guests 1   Bots & Crawlers 0