Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better UX when device has Airplane mode enabled or no Internet access. #40

Open
13rac1 opened this issue Feb 5, 2015 · 8 comments
Open

Comments

@13rac1
Copy link
Member

13rac1 commented Feb 5, 2015

Enable Airplane mode with no data or Wifi. Start the App. User gets a greyed/disabled Listen, but not greyed/disabled Speak button. We need a popup message to say "Yo! I need the bits and bytes man" Also, Speak should be disabled too.

@13rac1 13rac1 added this to the FAMSF Store submission milestone Feb 5, 2015
@hburgund
Copy link
Member

hburgund commented Feb 5, 2015

I agree there should be some notification, but Speak is left enabled on purpose since there is "offline mode" that allows users to make recordings, store them locally and upload them later when they open the app with connectivity.
Of course, this feature may not be desired with FAM's project, but it's a very useful feature to have in certain situations.

@13rac1
Copy link
Member Author

13rac1 commented Feb 5, 2015

@hburgund If that feature worked... Sure. Plus, the possibility needs to be clear to the user. Currently, pressing Speak results in a blank/white WebView in Airplane mode.

@hburgund
Copy link
Member

hburgund commented Feb 5, 2015

Like I said, some notification is needed. In iOS, I usually say something like "You have no connectivity, so you can't listen to streaming audio, but you can still make recordings if you want". Try putting your iPhone 4 in Airplane mode and see what happens.

The feature did used to work on Android as well, but I guess it's no longer working for some reason. Perhaps it's another one of those things that one of the long list of previous devs disabled for unknown reasons ;-( Obviously, it isn't needed near-term, but it should be re-implemented at some point.

Agreed that the near-term fix is to disable both Listen and Speak and notify the user as to what's going on.

@13rac1
Copy link
Member Author

13rac1 commented Feb 5, 2015

"You have no connectivity, so you can't listen to streaming audio, but you can still make recordings if you want" unless the webviews haven't been downloaded yet.

@multidynamic
Copy link
Contributor

It may be cool to use one of these icons: http://google.github.io/material-design-icons/

@hburgund
Copy link
Member

hburgund commented Feb 5, 2015

It is true that if the webview code hasn't been downloaded, it won't work. But since it takes network connectivity to download the app in the first place, the vast majority of people are going to open the app after downloading, thereby getting the webview code and not encountering this problem in the future. But I don't know if the Android app currently stores the webview files and only updates them when the version increments like it used to. If it requires downloading the zip every time no matter what, then this is clearly a much more significant issue.

Either way, if someone downloads the app and doesn't open it right away, but waits to open it for the first time at a time when they have no network connectivity, there would be a problem. For my iOS apps, I haven't worried about that edgy case, but there could of course be a series of different notifications or behaviors that are fully informative based on the specific scenario. We could also package the default webview code for Speak in the apk, I suppose.

@13rac1
Copy link
Member Author

13rac1 commented Feb 5, 2015

My preference (and therefore FAM's) is to notify the user of the situation and disable Speak functionality for the present. Long term, of course, I want people to be able to record without a network connection, but this feature needs so much work in it's current state.

@hburgund
Copy link
Member

hburgund commented Feb 5, 2015

Agreed...this is not crucial core functionality for the first release and this alternative approach is totally acceptable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants