Forum Discussion
QuickBaseCoachD
7 years agoQrew Captain
Out of curiosity why do you feel the need to do the development work in a high code manner, as opposed to doing this in a low code Quick Base methodology. Perhaps even design the app suitable for the mobile Quick Base App?
- ZintJoseph7 years agoQrew CaptainI have considered both. There are pro's and con's to both. I can build a mobile form and send the link to the people that have access to it....if they are somewhat tech savvy, they can create a shortcut to it on their phone.
The PWA option allows you to setup the link to prompt them to save to their phone. It sets up an icon on their device much like downloading an app from Apple or Google. The PWA option also caches the pages and information on their phone so if they are not connected to the Internet, the information and searches will still work.
Both solutions will work either on a phone or a computer so both options are valid. My manager asked for an "app" but the issue is that you would have to code it to both Apple and Google. The PWA is web based so would work on anything.
I am good with QB native mobile. More curious than anything if an "app" could be coded on code pages to do the same thing.
As I stated above, I did download a sample PWA and created the code pages for index.html, inline.css, app.js and manifest.json. I had to change some of the references to the src for the different pages and low and behold....it worked. The question is, since it is not on a server, will it really work.
I will most like build a mobile form solution within QB as a start and see if that satisfies my manager and go from there. - QuickBaseCoachD7 years agoQrew CaptainThe other advantage of a native Quick Base app is future supportability.