1 person found this helpful
I am assuming you are referring to apps in an add-on
There are no Jive specific things per se, you can employ a standard approach to designing a responsive app.. We've done a first responsive release of one of our add-ons recently:
Some things to consider though:
When viewed on a mobile device the Jive UI removes the Apps menu item, so you need to work with direct links to your app.
When changing between landscape and portrait mode, you need to manually resize your app canvas, as it does not seem to be detected by Jive, and you end up with multiple scroll bars (depending on your content)
Do you have any specific guidelines and or architectural details on choosing where to run your apps. Do you prefer the Node JS or use the regular tomcat server and run all the java script on the client browser. Any thought o this?
No specific requirements. Use what you are comfortable with. We use mostly .Net for our add-ons and host them on Azure. So a mix of C# for backend services and standard html/js for the frontend.