Does the Angular 2 router make sense in an Ionic 2 app?

Question

We made an attempt to move our Angular 2 application (written by our friend so that we could not know all the details) to Ionic 2. However, we have not yet managed to get it to work, so the questions below.

• Will Angular 2 Router work in Ionic 2?
• Does it make sense to use the Angular 2 router in Ionic 2 applications, or should we go straight to an alternative, such as DeepLinker ?

EDIT: I'm not sure what the current state is, but I read here that:

"The Angular router is currently undergoing intensive development and refactoring. As a result, the Angular s router has been disabled in Ionic.

3. Where in the code / metadata / build- script / package.json is the entry point that activates the router? We have routing in NgModule, but it does not seem to work when we access the main URL of the application and sub-URLs:

    @NgModule({ declarations: [ AppComponent, TestComponent, AgendasListComponent, TasksListComponent, SnackBarComponent, ConfirmationDialog, AgendaComponent, LoginComponent ], entryComponents: [ ConfirmationDialog ], imports: [ BrowserModule, HttpModule, MaterialModule.forRoot(), AngularFireModule.initializeApp(firebaseConfig, firebaseAuthConfig), RouterModule.forRoot([ { path: '', redirectTo: 'agendas', pathMatch: 'full', canActivate:[ RouterGuardService ] }, { path: 'agendas', component: AgendasListComponent, canActivate:[ RouterGuardService ] } ... 

Answer 1

I apologize for the last sentence. I was where you are too. And frankly, Jonah is a nightmare. It was good, though, for now ...

The reason we use Ionic is to develop once and deploy several times. web, mobile / tablet and possibly windows (linux?) ...

But the simple idea that the application we are creating looks awful on the Internet, like an extended mobile application. I tried, thinking that I would slightly correct it. But then I would leave the whole initial idea with a few basic codes.

This is part of the user interface. But then I found out that with the advent and development of Ng2, Ionic also decided to introduce NavController instead of waiting for a jet router ... And that where everything got messy ... So, besides having to worry about two code bases for the user interface I also had to rewrite it for router / NavController conflicts.

Meanwhile, my eyes fell on the Minks Gechev Angular Seed , and also successfully mixed the ion base with it.

After discussing silence on the Ionic Github issue, in which over 15 people shared my concern about the NavController issue. In which the Ionic core developer tried to silence us by telling us that "it will be resolved soon", in which I asked "to determine soon." He almost kicked me out.

Meanwhile, I was just tingling the Nathan Angular Advanced Seed . Nathan works for Telerik, the driver for the open source Nativescript (which is now a separate foundation)

At first I was skeptical, because Telerik, as a rule, exaggerates. I tried to shoot him, but he is really faster, and he is not a hybrid, he is native.

I like flexbox myself. So, I was looking for the user interface (web / windows) using it. Why not Onsen?

So, go to the seed of Nathan and take it into him. This is the interface. Backend - Keycloak and vert.x

Answer 2

Instead of using an Angular 2 router, it is recommended to use NavController and Co: https://ionicframework.com/docs/v2/api/navigation/NavController/ .

Ionic 2 also supports Deep Links in your application , as you yourself noted. You can read the official blog post here: http://blog.ionic.io/deeplinking-in-ionic-apps/ .

Here is the plugin for this https://github.com/driftyco/ionic-plugin-deeplinks , which allows you to create custom URLs that will open your application for certain views, if this is one of your requirements.