Over a million developers have joined DZone.

Ionic 2 First Drive: Making an RSS Reader

Although it's in beta, Ionic 2 is going to make a lot of developers happy. Here's what Raymond Camden found when trying it out.

· Mobile Zone

Visually compose APIs with easy-to-use tooling. Learn how IBM API Connect provides near-universal access to data and services both on-premises and in the cloud, brought to you in partnership with IBM.

 A few weeks ago I wrote about my experience looking into Angular 2 (Time for Angular 2?). I haven’t had a chance to dig deeper into Angular 2 since then but it is still high on my list to get more familiar with over the year. About a week and a half ago I had the pleasure of meeting Mike Hartington from the Ionic team at PhoneGap Day. I sat in his Ionic 2 workshop and came out convinced it was time to give it a try as well. And of course, just a few days later the Ionic folks released the beta version of 2.0. It is definitely beta, but I was able to build an incredibly simple app with it (after some help from Mike and others) and I thought I’d share my experience.

One of the most important things to note is that you can install Ionic V2 without screwing up your ability to do Ionic V1 apps or work with existing projects. It may sound silly, but as easy as npm can be, I didn’t want to have to worry about switching back and forth to work with existing projects. Heck, the CLI even defaults to V1 anyway so in case you forget, are in a rush, or whatever, it will continue to work the way you expect it to.

You’ll want to spend some time in the docs of course, and specifically the Getting Started guide. Note that there are mistakes in the guide (hey, it is a beta) that may trip you up. Specifically, it seems like some of the code samples are a bit out of date. For the most part, I think you can figure it out, but these issues have been reported and may be corrected by the time you get to it.

Working through the Getting Started guide gets you through a simple application and will give you a super basic idea of what’s going on, but I’d strongly urge you to go through the Angular 2 quickstart first just so things aren’t completely alien to you.

You’ll also want to peruse the components docs. From my quick look through it, things look quite a bit simpler to use, but again, this is still in development. A notable missing component currently is the loading widget. Be sure to notice that the component examples give you a quick way to toggle between Android and iOS views, and specifically that Android now has a Material look that is really freaking sweet. As an example, here are tabs in iOS:

iOS Tabs Ionic 2

Now compare it to the Android version:

Android Tabs Ionic 2

That’s damn spiffy.

So what’s the code like? As I said before, Angular 2 is different. Not bad different, just… different.

Like this...

While working on my first demo, I ran into things I immediately liked. For example, I love that my “page” template and controller are in a folder nicely packaged together. I could have easily done that in Ionic/Angular1 too I guess, but I like the organization.

I’m also really liking working with ES6. I’m barely scratching the surface of course, and probably doing it wrong, but even stuff I thought was overblown, like fat arrows, are really growing on me.

On the other hand, some things I ran into felt… wrong. I got over it. I also know there were things like that in Angular1 as well. But sometimes I just bit my tongue and went with it. So without further ado, here is an Ionic 2 version of my RSS Reader app. I did not build it out completely like the version I have on the Ionic market (RSS Reader), but I built in basic list/detail support. I’ll share the code, but I want to give big thanks to Mike Hartington (again), @adbella on the Ionic slack, and others.

Please do not treat this as good code! Treat this code like a slightly drunk cat walked over your keyboard and then had a little “accident”. It works - and the part that @abdella helped me with is elegant, but I’m sure I could have done things better. With that out of the way, let’s first look at the home page. It simply lists items from the RSS feed. First I’ll show the view:

<ion-navbar *navbar>

<ion-list inset>
<ion-item *ngFor="#entry of entries" (click)="openPage(entry)">{{entry.title}}</ion-item>

Nothing really weird here except the new way Angular 2 does attributes/code/etc. But I’m assuming you can figure out what is happening here. Now let’s look at the code for this page.

import {Page,NavController} from 'ionic/ionic';
import {RssService} from '../../providers/rss-service/rss-service';
import {DetailPage} from '../detail-page/detail-page';

  templateUrl: 'build/pages/home/home.html',
export class HomePage {
  constructor(public rssService:RssService, nav:NavController) {
      this.nav = nav;

      this.entries = [];

          data => {
              this.entries = data;


  openPage(entry) {
      console.log('open page called with '+entry.title);
      this.nav.push(DetailPage, {selectedEntry:entry});


So yeah - this is where things got a bit weird. One of the new things in the Angular 2 world is the idea of Observables. These replace (ok, not replace, but my understanding is that they are preferred) Promises and are supposed to be quite a bit more powerful. You can’t really see the Observable, but see the subscribe() call? That’s using it. Part of what makes them powerful is that they would support live updates. That doesn’t really come into play with RSS parsing, but if it ever were added to my project, in theory, it would just plain work. (Note to self - I’m going to try to make a demo of a live updating Ionic 2 app soon!)

Also, note the navigation in openPage. I don’t have to build an app router now. I just load the page and pass data. I really, really appreciate that.

Let’s look at the service now.

import {Injectable} from 'angular2/core';
import {Http} from 'angular2/http';
import {Observable} from 'rxjs/Observable';
import 'rxjs/add/observable/from';
import 'rxjs/add/operator/map';

  Generated class for the RssService provider.

  See https://angular.io/docs/ts/latest/guide/dependency-injection.html
  for more info on providers and Angular 2 DI.

//Credit for latest version is @abdella from the Ionic Slack
export class RssService {

    url = 'https://query.yahooapis.com/v1/public/yql?q=select%20title%2Clink%2Cdescription%20from%20rss%20where%20url%3D%22http%3A%2F%2Ffeeds.feedburner.com%2Fraymondcamdensblog%3Fformat%3Dxml%22&format=json&diagnostics=true&callback=';

    constructor(http: Http) {
        this.http = http;

    load() {

        return this.http.get(this.url)
            .map(res => res.json())
            .map(data => data.query.results.item);

      /* v2
      return Observable.create(s => {

        this.http.get('https://query.yahooapis.com/v1/public/yql?q=select%20title%2Clink%2Cdescription%20from%20rss%20where%20url%3D%22http%3A%2F%2Ffeeds.feedburner.com%2Fraymondcamdensblog%3Fformat%3Dxml%22&format=json&diagnostics=true&callback=').subscribe(res => {
            console.log('in sub');
            var result = res.json().query.results.item;



    // Static version     
    //    let data = [{title:"do one"},{title:"do two"},{title:"three"}];
    //    return Observable.from(data);

I apologize for the large blocks of commented out code, but I wanted to keep a record of my previous versions for reference later. The slick http.get().map().map() syntax is an example of Oberservables in action and is thanks to @abdella. The basic idea here is we're fetching the remote data, converting it from a JSON string into an object, and then specifying a precise part of the result to work with (data.query.results.item).The imports on top are a bit weird. Specifically the fact that we have to import specific parts of Observable. It seems to me that if I want to use a library, I don't want to have to worry about parts of it being "optional", and basic functionality like I used doesn't seem like it should be optional. This is one of those parts that bugged me and I just got over for now. The detail page is pretty trivial as well. Here is the view:

<ion-navbar *navbar>

<ion-content padding class="detail-page">
    <div [innerHTML]="entry.description"></div>

That last bit, [innerHTML]=, is how you handle rendering HTML in Angular since it is still a pain in the rear about it. (Yes, I know there are reasons, and yes, it still bugs me.) The code for the page just picks up the passed in data. Again - this is really super easy I think.

import {Page,NavController,NavParams} from 'ionic/ionic';

  templateUrl: 'build/pages/detail-page/detail-page.html'
export class DetailPage {
    constructor(nav: NavController,navParams:NavParams) {
        this.nav = nav;
        this.entry = navParams.get('selectedEntry');
        console.log('my entry is '+this.entry.title);

Here is the home page:

And one detail page:

Not exactly rocket science, but you get the idea. So far, I’m digging it. I’ve got a lot of research to do, and I’m really looking forward to when things hit a firm release and stop changing, but I’d definitely take some time to look into it. As a reminder, you can, and should, join the Ionic Slack channel. It is the best place to get support and help others.

If you want a copy of my app, you can find it on my GitHub repo here: https://github.com/cfjedimaster/Cordova-Examples/tree/master/rssreader_ionic_v2.

The Mobile Zone is brought to you in partnership with Strongloop and IBM.  Visually compose APIs with easy-to-use tooling. Learn how IBM API Connect provides near-universal access to data and services both on-premises and in the cloud.


Published at DZone with permission of Raymond Camden, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}