Docebo's Go Learn App and Branded Mobile App

Hi Colin, 

With the app, can a user purcahses courses?

Thanks

Colin

@colinfarrelly88  Currently within the Apple Store the Branded and Go.Learn Apps do not support courses being purchased. Learners can purchase courses on the desktop and access/complete purchased courses on the App.

@colin.schott thank you so much for the quick reply, our issue is people come to our site to buy a course and then they are prompted to downlaod an app, they download the app thinking they will now be able to buy the course when they cant, its a litte annoying. Do you reckon mobile phones would work ok without the app?

Thanks

Colin

@colinfarrelly88 Using the Safari/Chrome browser to go directly into your platform would work as it is not part of the App.

@colin.schott  While users buying courses is a small part of our area, users are mainly enrolled into courses by us and do not have to buy courses,  they too would use their phone for doing courses.Would gettitng rid of mobile app and use safari or chrome instead,  affect the quality, user functions, tracking and course completions?

Thanks

Colin

@colinfarrelly88 Nothing that we have reported nor would we expect to have a difference between the two?

@colin.schott oh great we might get rid of the app then so, but if this is the case what is the benefit of the app if its a littel annoying for theuser to download, find url  and log into? Also thank you so much for your quick response and help

Hi @colin.schott , 

Loving that I can have some analytics from the courses and this is really useful. I was wondering if there was any way to tell if someone has accessed an asset from the mobile site?

gmail “sso” plugin works fine in go.learn but crashes in branded mobile app

I’m not the only customer with this issue.

@lrodman I would recommend opening a support ticket for Docebo to look at this issue.

Hello, 

I’m looking for a comparison of available features/capabilities between Browser and Go Learn app. Also what’s the roadmap for Go Learn app. 

I’d like to see this differences document, and the Docebo mobile road map as well.

Our users generally find the go.learn app is confusing to set up properly, so we are referring them to Safari or Chrome on their device.  

Before we licensed Docebo, I evaluated several LMS vendors who have stopped developing their apps in favor of a browser-based approach. 

I’d love to see this comparison.

How is go.learn hard to set up? The login and domain aspect? We’re using branded mobile and bypassing that. So far so good. Publishing to the apple store was a B** and a half. As in Boo! Happy halloween.

Docebo DOES seem to be making a legitimate good faith effort to bring a piece of browser-docebo to the apps each month. Sometimes it’s things that seem low value to me personally.

That’s a great point. I initially thought the Docebo app setup would present no major problems. Many of our users have limited tech skills. For example, we often have to explain how the shift key is important when creating passwords. A significant number of our users use a primary language other than English. There are many possibilities for confusion, and its easier to direct users to our doceboSAAS URL or the link on our employee web site. 

Ours aren’t QUITE that limited in tech skills, though I’m always surprised how many people want to call vs zoom for IT support.

Very few of our users access on mobile and the few that do seem to be happy using Safari or Chrome. I know Docebo recommends using the app, but what are the main advantages of the app over a mobile browser?

Offline. That’s all IMO. And that’s of minimal use. 
 

I would normally say it avoids ugly titlebars and letterboxing, but IMO a those are worse in the app…

Is more than one app need for multi-language support with the branded mobile app?

If we have a single app where users drop into Root but two different languages, what are the considerations?

Or it is just cleaner to manage multiple language support with two different apps?

@jessica.sanderson Not required, for multi-language support. The app should display the language the user has selected. Having several branded apps allows you to have different branding and support EE options.

We are looking to hopefully launch the Mobile Branded App in the next 12 months or so but before we sign and take the plunge we’d really like to talk to a team who have already launched. Our AM is putting out the feelers internally but also suggested we reach out on the Community. 

We’d really like to understand how the onboarding and launch went, what ongoing administration is like, lessons learnt/what you’d do differently, what benefits the app has brought to your learners and possibly give a demo!

We’d be really appreciative for anybody who is willing to help! :) 

Not sure if this is still being watched.. but if I use a token with one name before publishing (while my boss is on vacation this week) and she comes back and decides we need to change the name would we be able to do that? 

I want to use the token and get us as far as we can before calling in IT. But I’m nervous to use a token with one name and then need to change the name and not be able to… 

I have stupid questions …. are there any guidelines beyond this page here” https://help.docebo.com/hc/en-us/articles/360020080940-Branded-Mobile-App-Publisher#h_01G396JY1KZNGQAYK7MA9N6FTP

On how to set up the App for the App store…. 

I’m feeling a little frustrated because the app store needs information from docebo, which I can’t seem to get from docebo without getting information from the app store… 

Also, I’d love some guidance on setting up the privacy details for the docebo app ….  for example the data collection… does the app collect data?

https://developer.apple.com/app-store/app-privacy-details

I am sure this is mostly user error and unfamiliarity… but any help would be appreciated

Stupid question: how do you answer about user data for Google Play and Apple Developer? 

I found the answer here for google Play - https://help.docebo.com/hc/article_attachments/8065350971922

Although that documentation is wrong because it says name, email, username are not collected then it says to answer that they are collected in the form. So someone @Docebo should probably update this documentation if possible. 

Also question for you @colin.schott The instructions for Google Play tell you to resign the app but when I resigned the app and uploaded the app to Google Play, Google Play wouldn’t accept it because the key did not match the one that was in the Google Play account. 

I uploaded it without resigning and it seems to have worked. It’s ugly but I think that’s because I didn’t customize the mobile settings yet, but I was able to login and poke around and things seem to work as expected.

Why do I need to resign the App for Google Play? And if I have to resign the app, how do I get Google Play to accept it when the SHA doesn’t match?