July 2016 Summaries

Raymond Camden, a Developer Advocate at IBM, explores the use of the Ionic Native framework, which offers an Ionic/Angular-friendly interface for Apache Cordova plugins, by demonstrating how to implement the Device Motion plugin in an Ionic 2 application. This plugin allows developers to monitor a device's accelerometer to trigger events based on device motion. Camden's project involves creating an app that displays a list of data, which can be refreshed by shaking the device, showcasing a practical application of the plugin. He details the process of setting up the application, including creating a provider to manage data and utilizing the Cordova Tools extension for Visual Studio Code to simulate device behavior. Camden explains the logic behind detecting a "shake" event by comparing accelerometer values and adjusting the app's response accordingly. The article emphasizes the importance of testing on actual devices to calibrate the shake sensitivity and provides a link to the complete source code on GitHub for further exploration.

Ionic Native is a project designed to help developers utilize native SDK features in apps built with the Ionic framework by offering a centralized repository of Cordova plugins, making them easier to find and use with consistent APIs. It addresses the common misconception that Cordova/PhoneGap cannot access the same native features as pure native apps by wrapping supported plugins with TypeScript decorators that add Promise, Observable, and Typing support. The project has grown significantly, offering nearly 75 plugins, and it has replaced ngCordova to provide better support across different frameworks, including Angular 1, by integrating directly into Ionic 2 projects. With Ionic Native, developers can expect improved debugging features and a framework-agnostic approach, ensuring that web technologies can leverage native mobile capabilities efficiently.

Ionic introduced the Ionic Cloud Wish List to engage with its community by allowing users to share and vote on ideas for improving its backend services, which are designed to simplify mobile application development. The platform encourages community feedback by enabling users to post comments and discuss potential features or products. Ionic also implemented a system to update users on the status of suggestions, indicating whether they are completed, in progress, or on hold, with additional explanations and links for more information. This initiative aims to streamline communication and keep users informed about how their ideas are being addressed.

Integrating JavaScript libraries with TypeScript in Ionic 2 applications can initially pose challenges due to TypeScript's inability to understand additional code, but using Typings can simplify the process by managing type definitions. Typings, which helps TypeScript recognize different JavaScript library types, can source definitions from various repositories such as npm, GitHub, and DefinitelyTyped. A common issue arises when dealing with global definitions, such as the ES6-shim module, which requires specifying its global nature to the TypeScript compiler. Despite initial frustrations, with proper setup, TypeScript projects can seamlessly work with JavaScript libraries, enhancing development efficiency and compatibility.

Jonathan Grupp, a software engineer at M-Way Solutions and a contributor to Ionic, concludes his three-part series on building robust Ionic apps with advanced workflows by exploring environments, CORS proxies, and build tools for app icons, splash screens, and app delivery. This installment focuses on managing different API endpoints using environment variables, handling CORS issues with built-in proxies, and automating build processes with Gulp tasks, including injecting variables from the command line. Grupp emphasizes using the Generator-M-Ionic to streamline development workflows and build versions for different environments, while also discussing the integration of Ionic Platform services for app delivery. The article reflects on the evolving landscape of app development with emerging technologies like Angular 2, Ionic 2, Typescript, and ES6, inviting feedback and ideas for future updates.

In the second part of a series on developing enterprise-level Ionic apps, Jonathan Grupp, a software engineer at M-Way Solutions, delves into advanced workflows crucial for creating robust applications using the Ionic framework. This segment focuses on integrating quality assurance measures such as linting with ESLint, unit and end-to-end testing with Karma and Protractor, and automating these processes using Husky hooks. Developers are guided on adding Angular components, Sass styling, and Cordova plugins to enhance app functionality, with tools provided to streamline these tasks. The process of using Bower packages for additional features like language support is explained, alongside instructions on testing apps on devices using the Cordova CLI. The article emphasizes integrating the Ionic Platform's ecosystem for backend services, offering a comprehensive approach to elevating app development proficiency before moving on to more advanced topics in the subsequent part of the series.

Jonathan Grupp, a software engineer at M-Way Solutions, introduces a three-part series on advanced workflows for building robust Ionic applications, focusing on Part 1 in this piece. The series details the use of Generator-M-Ionic, an open-source tool that facilitates the development of scalable enterprise-level applications by integrating with the Ionic CLI and addressing complex project requirements such as testing, quality assurance, and continuous integration. This part outlines the initial setup process, including installing necessary tools like Node, Bower, Yeoman, and Gulp, and guides users through creating their first project with Generator-M-Ionic. It emphasizes the importance of a standardized project setup that simplifies development, allowing for seamless transitions from prototypes to full-scale applications. The article highlights the integration of Git for version control, ensuring that only essential files are tracked, and encourages readers to explore further in the subsequent parts of the series, which will delve into quality assurance, ecosystem integration, and backend management.