I am using Oracle Apex 4.2.3 for the internal applications of my organisation. The end user base is fairly small. Almost 80% of usage is in desktop and the rest is in iPad. In general, i like to use standard templates (theme 21/23 etc.) rather than responsive template 25, the reason being my primary target audience is in desktop. I do use Inline CSS (thanks to F12 developer tool bar) a lot in all my pages to customize the pages to render in a usable format in iPad. Sometimes i customize report/page templates. for e.g. i create my own "report template custom" where all reports have rounded corners/different backgrond colours etc..
I could have developed the application using Autodetect and a separate Mobile User interface. But due to time constraint, i prefer not to do it. I just do one application targeting desktop users predominantly. I use inline css on pages which would not render nicely in ipads. I don't have much control/knowledge in setting up of Apex v5.3. My database administrator does it for me. We are hoping to get it in the near future. My biggest concern until then, how will my "inline css for ipad only" behave in a scenario where my dev environment gets upgraded to v5.3. Has anyone got an experience where you upgrade your application from v4.2 to v5.0 (or from v3.2 to v4.0) and see all your inline css/customised templates going awry ?
I have relatively limited (almost none) experience in upgrading apex applications. i have never worked in versions prior to that of 4.2. Would appreciate any tips on how you would handle application development in apex when you know that 80% of your users are in desktop? My co-worker thinks i should still go with responsive theme. There are already too many applications in responsive theme 25 (v4.2) in my organisation. They all look very similar in look/feel. i find it bit boring.. That's why i like to use other scarlet themes such as theme 21.
- Go Responsive
- Do 2 user interfaces (desktop/jQuery Mobile)
- Do 1 user interface (Desktop) - Customise pages using CSS
I went with option 3. But not 100% sure it is a wise choice..