@viktorgullmark wrote:
Hi all!
I’ve used Ionic in the past, but only for mobile alone. I’m about to start a new project and am still in the decision-making process of choosing frameworks and Ionic is the plan as of now.
My problem is that I don’t know if it’s suitable to use Ionic alone for this project, or if it complicates things for the desktop-development. I know Ionic supports desktop, but I don’t want it to be a struggle compared to building pure desktop outside of Ionic.
The app I’m building will be targeting desktop in the first hand, but we think a great portion of our users will use it directly in their mobile browser, which is why we’re considering Ionic. We do not have any plans on releasing it as an app in the stores, since we don’t require any native functionality at all.
So, I’m leaning towards these two options, and would love your guidance on this:
1.) Build everything in Ionic, even if the main-target is desktop-browsers
2.) Build the desktop-browser part outside of Ionic (in pure Angular), but with a shared code-base that extends to our Ionic app which will be used for mobile. So in reality two apps but with shared code in-between.My main concern is that option 1 will complicate things, compared to running Angular alone, since Ionic is built for mobile in the first place.
Thanks for your input!
Posts: 1
Participants: 1