Feature Requests

We assume that we are seeing full performance from our paging servers and that the apps are reaching the clients as quickly as possible but how can we be sure? I'm thinking it would be cool if AppsAnywhere had a single, large appset that customers could load in the system and then time how long it takes to reach the client. We are only interested in the time it takes to page the apps to the player so the appset would only consist of files and folder and would not actually be an launchable application. The recorded time would be compared with other customers / environments. AppsAnywhere could also create baseline times using their own environments.

When a university has decentralized IT departments, they cannot restrict or delegate admin rights to specific parts of the Admin tools to individual users. Similarly to restricting students' visibility to apps by log-in, Admins would only have access to what they are allowed to do.

Could we bring back embedding HTML markup into the app description. We have a scenario where we have different teams packaging for us who do not have access to the Admin portal. We then use their provided HTML description and format this ourselves to add. It's cumbersome and would be better if we could just copy/paste the HTML code into the description field as it was done previously.

AA has the ability to install apps provisioned through the Apple App Store through Jamf's Mac apps, but some apps are not available through that. As an example, the Minecraft Education Edition app; which is only available for iOS in the App Store. But Jamf has the Desktop version packaged in their Jamf App Catalog.

A new community driven Cloudpage packaging and recipe site. Where packages and\or recipes can be submitted for peer review and published. Submitted packages would of course have to meet certain naming convention standards and there might become some duplication of Cloudpage packages across all of the AppsAnywhere users. The benefits of though could be that new version and patches to small les troublesome applications are more likely to be addressed faster. This would help to keep the security bods who don't follow the benefits of containerised applications at bay. Users should be able to follow and favourite their key applications, and be notified if a new version is available to test, check and use at their own discretion. Perhaps a peer based rating scheme for the .stp and recipe's submitted to allow some filtering. (This would leave yourselves to concentrate on the complex auto-license packages also) You could even offer some form of prize for top packagers. ;-) Andy

I'd like to be able to see when a session was started so I can have more information on deciding if I can Evict a session or should be choosing to Upgrade instead.

We would like Analytics to be able to show user details and their individual run times for specific apps. By viewing the usage of a particular app (and it's users), the following fields in a report would assist with making informed decisions regarding software renewals/appropriate licensing: * App Desktop Name or ID * With a filter for usage in the past 12 months * Device Name * Username * Launch Date/Time * Total session Run Time Currently the data is incomplete as the Launches Explore can show the number of user launches and their devices, but unable to show how long a user used an app for. ie. if an app was not working properly you would have no way to show that in this report as it would show as launched but actual run times might only be seconds (so it would not be obvious that there was an issue). Similarly the Run Times Explore shows how long an app was used for but not who the users actually are (ie. we would want to filter out tech staff that are testing apps to determine actual and accurate usage of an app). Can you please provide this type of report? (Refer support case# 34366 for further details)

This function would make it easier to see the user's view of the portal, no matter what OS or version. This could be implemented for instance as follows: From Admin-console, select Portal (or Mimic OS/version) with choice of OS: Default (i.e. same OS as that of the admin user) macOS (and version) Windows (and version/variant) etc. When in Portal, show Admin that Portal is in OS simulation mode, with OS/version/variant (header of browser/top of portal windows) And of course instruct the portal that this is the OS running so that the admin can see what apps are available, try to launch downloads, run on servers etc. (Ideally) block and inform the Admin if trying to launch apps from non-compliant OSes. Return to Admin to exit this mode

Server 2016 / 2019 / 2022 are bundled I'm assuming 2025 support is in this as well. At a minimum, Server 2016 should be separate as it behaves differently. As an example, I have a package that is over 2GB in size due to compatibility with Server 2016. This could have been 200mb if 2016 wasn't bundled (and a separate package for 2016 only). Thanks, Paul

Feedback from 2022 user days. Customer wants it to be easier to push images out using Intune via AppsAnywhere