I’ve had some time to think and research since my original comments. Perhaps I’m still a bit confused, but I may be able to state my desires and concerns more clearly. Please help me understand better if I’ve gotten something wrong.
There were several reasons I originally picked meteor for my project. It combines a Angular2/Ionic2/Cordova core of functionality with some additional functions like authentication. These are capabilities I could build on my own, but then again I’m not part of a large development team. I freely admit I’d prefer someone else implement some of the hard parts. And finally, mobile solutions for IOS and Android are critical to the project’s success.
I think I’m starting to understand the impact of the different packages on what I need to do for a successful project. First, there is the split between web and mobile. The tutorial introduces the idea of creating two different sets of HTML (and initialization), one for the web application and one for the mobile apps. This makes sense from the Ionic/Cordova side, since the Ionic HTML elements are used to generate the native mobile apps. While the web app could also be generated by Ionic, I assume adding another layer would impact performance. It’s a reasonable tradeoff that doesn’t greatly impact development.
The second impact of the packages is on layout. When I originally asked about Angular Material, I was concentrating on layout. And because of the web/mobile split I mentioned above, this is primarily for the web side. A good deal of the mobile layout will be dictated by the Ionic HTML elements, as well as the native components.
What are my choices? I could concentrate on mobile while waiting for one of the packages to implement what I need, augment the layout side of a package with a more complete UI element package (like PrimeNg), or create my own missing UI elements. I’m leaning towards the last option and doing some prototypes.