Go to Site Settings > Assignments, and there you can assign apps to different types of actors. If you set to Optional, the actor admins or person can decide to enable the app or not, otherwise. If you set it to Always, it shows on all actor profiles.
Are you building a custom template? The plyr library should be included in the main js library of Anahita. Anahita doesn't support gif files yet, because animations require some extra steps for resizing.
Don't go too elaborate on customizing Anahita's layouts. Once the Anahita React App is ready, we are removing the entire HTML layer from Anahita and turn her into an API only service. This transition will likely be complete in 6 to 8 months.
Wuaah. So not much left from the Koowa / Nooku framework.. This is super crucial. I can remember a discussion a few years ago: Switzerland still has 4 Languages. Belgium has 3, Luxenbourg has 2... What you estimate for the effort now to get this done ? Its already the comom 1 Moaning Point: "Its english", my Russian Friends moaning, we sent you a translation for russia, where it is :-) Make me a quote, but quick, and stream module for Groups or Peoples for Joomla and GravCMS please. I need it - lets have a call
No there isn't any Kooka and Nooku framework left. It's all Anahita now.
The feature you are asking for is natively supported by client-side apps. Right now when you develop a mobile, desktop, or web app, the app can detect the native OS language setting and use the appropriate translation file. We have that working in the Anahita React too.
Anahita is moving to become a client server architecture. Once the Anahita React app is ready, we are going to remove all the parts that are responsible for user interfaces and language files in the Anahita codebase. What we keep is the graph architecture and API layer. Views will only have JSON outputs.
If you are building any projects right now, I recommend building a client app for the user experience part and use Anahita as the back-end API only.