Just like the User function, there should be a Device function where you can pull the type of device and maybe some manufacture info, serial, something.
App.Version and App.Device (in addition to App.ActiveScreen) is under review.
1. one Central-mobile-App -> take on mobile-handheld home screen (right three points -> "apply this to home" and hide/delete the original powerapps-icon from home-mobile-screen)
1. one Central-PC-app -> give this URL only to the PC-users and they should save it as favorite or so...
....or do I misunderstand your needs?
@move-on, I have not yet found a way to force a PowerApp to open in the PowerApps mobile app. I think the only way to do this is to open the mobile app and then launch the PowerApp from there. I have tried using the weblink and the appID, but they only open in the browser and not in the PowerApps mobile app.
If I am designing an app specifically for mobile, it's usually because it has a mobile-only feature such as image capture with the device camera. If you open one of these apps in the browser on a mobile device, you will get a message that the mobile specific features will not be available and to access those features you must install PowerApps and open from there.
So from what you described it would defeat the purpose of designing apps with mobile only features as they would not be able to be used.
-> for mobile/handheld (Android): as described above, if you open the powerapps-App and then you see the apps and can push on the three-points (vertical) right of the relevant app and select "send it to home" or something (I have no english-app here unfortunately). Then you´ll have your "Mobile-CENTRAL-App" e.g. as icon on the mobile screen and can delete the powerapps-icon from the screen...
-> for PC/Browsers: In Powerapps-Studios there is a links in the section -> PC-Central-App -> three points (horizontal) -> Details -> see WEBLINK, this is the link for PC-users,
-> did you know this and/or can you work with this?
@move-on I see what you are saying now. I misunderstood.
This may work well if you only are using a few apps, but if you have a larger number, it could get cumbersome and bulky, even if you group them. Plus there is the time involved in making 2 versions of an app and keeping both up to date.
If the issue can be solved with some basic device detection that would be much better in the long run. There is an article out there about making truly responsive apps that I am going to look into soon that will hopefully alleviate some of the pain points around accessing via pc, phone or tablet.
Detecting the device would just be the icing on the cake. And I don't make the policy about how we do PowerApps in my organization. I have already brought up the idea of having 2 apps, one for phone and one tablet layout and it was shot down.
I agree this would be nice. For example, created a mobile app hoping to use it on a surface pro, but the camera component on surface pro does not work with powerapps. It works great on an ios device or android device, but Microsoft can't seem to support their own products...go figure. This would allow you to shut off the option or at least post a warning that the app works better under a web browser than in the powerapp application.
Sad that my greatest motivation for this is to be able to give a warning to Microsoft Surface users that a microsoft product does not support their product well.