User Interface Issues

[gebhard 3]

Hi,

 

I've some UI issues with the Emby Android app:

• Android: 5.1.1 (on OnePlus 2) and 5.1.1 (on Xoom, OmiROM)
• Emby: 3.0.5821.0

The naitve UI of the app fails to display many kind of content. But when using the web display option (within the app (manage server -> click the URL "Local Access"), not a browser), everthing works fine.

 

• channel view native:
• channel view web:
• my plugins native:
• my plugins web:
• plugin catalog native:
• plugin catalog web:

App log: abeff4e2-2990-47cc-877a-d09bd691bcdd.log

 

Any ideas?

Thanks,

Gebhard

 

[Luke 36992]

Channels might just be taking a little time.

 

As for plugins, right now that is by design but what I'll do is just hide the whole section to avoid the bug reports. If we're going to allow the plugins to be displayed in-app then we would first have to vet all of them for store compliance. I know a lot of the ones built by community members have paypal donate buttons, and displaying that in-app would violate play store policy.

[gebhard 3]

Nope - Channel content doesn't appear (and why should it take longer to load it natively within the app vs. through web within the app?).

 

I can't see and difference regarding compliance when content is displayed in the app - either natively or using web interface. The user can't see any difference, it's both within the Emby app. If the web interface would load in an external browser, this would be different, but it loads within the Emby app.

 

And BTW - why should I not be allowed to see my installed apps in the Emby app anyway? I'm not speaking about community apps, but apps loaded through the integrated app store.

[Luke 36992]

What do you mean installed Emby apps?

[gebhard 3]

sorry - too early in the morning .. it should read:

 

And BTW - why should I not be allowed to see my installed _plugins_ in the Emby app anyway? I'm not speaking about community _plugins_, but _plugins_ loaded through the integrated _plugin_ store.

[Luke 36992]

Many of the plugins in our plugin catalog are built by community members and have not been vetted for app store compliance. We'd have to go through each and every one before we can display them. We may at some point take the time to do that, or perhaps maybe we'll only allow the ones that are developed by the core team. I'm just not sure yet. Until we have the time to really look at that it's safer for us to just hide them altogether.

[gebhard 3]

OK, understood.

 

But as I said: as long as you load the web interface within the app and not in an external browser, the plugins appear within Emby app if you click the "local" link in the manage server menu. So all the non-approved plugins appear in the app through the web interface...

 

But if you kick the plugins out of the app and load the web interface in an external browser, this would be quite fine for me.

 

Then there is the strange channel problem - let me know if you need more information.