One thing we learnt: Appgyver for mobile app development
We recently introduced Jerry Lu, Web Developer with the IDX team. Jerry’s background is in social web app development, particular experience with Social Engine, the system that underpins the Community of Excellence. For some time we’ve recognised a need for us to deliver native mobile applications (as opposed to responsive web apps), but we wanted to leverage our collective expertise in web technology (like HMTL, CSS and Javascript). So cross-platform mobile development frameworks such as Appcelerator were of great appeal, but we’d heard some mixed reports about performance and stability, so we wanted to test and evaluate. Here Jerry reports back on a promising option that we’ve evaluated and are likely to use moving forward. (Note that we’ve also got some thoughts re: backend that we’ll hopefully be able to share in future instalments.) ^GY
This post is designed for developers who are seeking for a way that can develop hybrid mobile apps with native performance and convenient options for deployment. We've been looking at these issues, and have trialled what we think is a promising option/framework called AppGyver. In this post I'll outline our take on it and why we think it's a good option. AppGyver consists of Supersonic as the framework, Steroids as the tooling and AppGyver cloud build service. It supports both iOS and Android mobile device operating systems.
Supersonic is an Ionic fork that might changes way you think about hybrid app performance. I think it's a game changer. AppGyver leverages common web standards/technologies such as HTML, CSS and AngularJS. Supersonic uses native UI elements. Page transitions, modals, navigation bars, tab bars, drawers—and a whole lot more—are fully native. That results in a very strong performance. Supersonic also supports multi-page apps which improves the performance more than I expected. No more worries about the rejection by Apple store because of performance issues.
In terms of development, Steroids provides flexible ways to meet developers' needs. To deploy the build to a device can be as as easy as scanning a bar code. Once the connection between AppGyver tools and your device is established, the app can be downloaded automatically to your device when the developer modifies the source code. No need to deploy the app manually—saving time. If you prefer to use the emulator instead, Steroids also supports debugging in Safari.
Also, the AppGyver cloud service is just great and convenient. After setting up all the options you want, the AppGyver cloud service will help you get through the process to generate a standalone build for debug and release. Only thing to do is click the button via your AppGyver cloud account. Deploy the build to cloud.
Then let AppGyver cloud service to generate the build. In minutes, you will receive a mail from the AppGyver cloud service with a download link to your build which is ready to deploy to device or publish. The AppGyver cloud service makes the build directly instead of generating build by Xcode.
In summary, AppGyver is more a kind of service than a traditional library which developer only can include in the project. As a web developer crossing over into the mobile development space, I've found AppGyver to have all the functions I've imagined/needed covered. But it provides even more value for development team by streamlining the whole development process and simplifying debugging.
One potential downside is that the development team needs to pay a annual subscription fee for an account with the AppGyver cloud service. But the yearly cost is reasonable for a team of developers. In my opinion, it is worth to have this cloud service because the AppGyver team also provide further support. The developer also can use the add-ons which includes a collection of premium, turn-key implementations for common mobile app features.Correction (25 May): We've been informed that AppGyver's cloud service is free for use. Charges relate to the Add-Ons and premium support options.