I had a quick test yesterday with AppGyver to try getting the web app built. I used the basic default app and went to Launch>Distribute tab> Configure and then ran the build. It came up with Status created but that just means that its processing it.
Later I got an email saying that the web-app had been created and there was a download button that would allow you to download a zipped file of the webapp so you could load it onto a server.
I first displayed the webapp in my browser on my PC and of course the proportions were all wrong so I sent it to my phone and results as below image
WebApp Uploading to Server
I took the downloaded web app and moved the file onto my server. For one of my websites which is active I loaded the files into a sub-directory and was able to open it in a browser, so that it becomes an accessible webapp.
Create an APK
So my next exercise will be to create a keystore file and see if I can create and install an android app. I’ll start with a simple blank as before as the test is in the process, not the actual app itself at this point.
After adding the java SDK path to the keytool.exe file into system variable path I should be in a position to be able to create an APK file.
and added password that needs to be 6 digits long minimum.
Anyway, following the steps of the video it all went fine and I did a build on the app and got an email about 1/2 hour later to say I can download the zip file.
This I did & then after unzipping the file there was a file application.apk. I renamed it testmax.apk
I then tried to copy to mobile phone from computer with USB/micro USB with USB C attachment but the phone did not register the device, so I had to use MicoSD car to copy files across. Uploading the .apk file it opened , with warnings, the app on the mobile phone.
There was also a file called Bundle.aab and that is a special file for loading app to Google Play, so that they download less onto peoples phones. So it generates that file too. Not equired if you are doing a direct load to your phone
Seeing what is created in the web-app build I’ve an appreciation of what is actually happening. There is the app developed in Composer pro , then it is put through 3 different automations to create either Android, iOS or Web App. All the processes are different and are external formats based on the different OS’s, so that build process will need to be updated each time a new OS is updated.
So whereas Glideapps is all just web apps, this is building for 3 different install methods. So the tools need to be more robust and the features need to be viable in all 3 environments.
This means the resultant app can be distributed in a variety of ways, to suit specific flavours.
Also all of them have better distribution systems such that you can come away with a separate app that you can share in multiple ways, either via a URL from your server for the web app or a downloadable APK file for android and a whatever for apple.
So the end result is a free standalone tool, which is great. The reliability and lack of information on first using it is a concern.
App information and layout
I watched a couple of videos this morning about AppGyver, one was about a pizza app and the setting up of the layout just looked painful and tedious. Still, I suppose there is no way around that. Lots of fiddling though.
The 2nd thing I noted that containers seemed to be the way to divide up your screen into items like Navigation (linking pages and menu’s etc), Logo area, content and buttons. Also that there were scrolling containers, these allow you to add lists to have multiple items.
When I was watching the pizza app development I started to wonder about where the data was kept and how you accessed that, that is an area I want to explore a bit more to see if I can store data in a sub-directory somewhere but I did note that you can use a firebase database to store info too, as well as hooking into an API
I was unimpressed by the permissions when creating an android app in the build in that it seemed to only have access to things like camera and fine location and mic but not to sensors. I stand corrected as you can access these on your app, I found some documentation here
SAP only bought out AppGyver this year in feb , see article. Also AppGyver from Helsinki, Finland. So maybe when I was trying to run it was in middle of night over there and everyone was to bed and asnoozing. So they only found out issues when they came in in the morning.
Today I was able to:
generate builds for the basic default template and configure and build a web-app that I could download.
Move the files to my VPS and install them on an active domain and access that app from the browser.
Configure and create keystore file and configure and build an android app that AppGyver was able to generate a zip file that was downloadable.
The zip unloaded had an application.apk (that I renamed) and I transferred that to my phone and was able to open the app.
So the program allows me to create, build and serve apps either as a webapp or as an android app.
I suppose I could go further and pay $25US and get a developer account and upload it to Google Play, but for the time being I’m happy being able to create a web app and an android app.
Its worth taking the next step and start using the program for its features.
So the decision now is what do I want to build? I think I’ll have to look at configuration to see about displays for phone or web pages for apps.