Ionic is a great framework, and the guide you link to is really nice, but to be honest I'd try out React by itself for a while before I dove into frameworks like Ionic or Gatsby or Next. If you understand the fundamentals first, it's easier to learn what's a framework and what's React APIs.
Well I would say that using Ionic with React is using React by itself.
Ionic isn't a framework, it's a UI components library.
Therefore the fundamental remains the same. Components, functional components, hooks, react-dom, JSX, state, or even redux and all other subjects, etc. same same.
But of course, what's really important, is to find the way which fits you the best 😃
Well, let's not split hairs. Framework or component library - Ionic is really cool, and it makes it very easy to make cross platform apps. The reason I suggest that you learn React by itself first, is that you don't have to learn the APIs of Ionic at the same time.
But for sure - finding your own path is important ✌️
Ionic is a great framework, and the guide you link to is really nice, but to be honest I'd try out React by itself for a while before I dove into frameworks like Ionic or Gatsby or Next. If you understand the fundamentals first, it's easier to learn what's a framework and what's React APIs.
Well I would say that using Ionic with React is using React by itself.
Ionic isn't a framework, it's a UI components library.
Therefore the fundamental remains the same. Components, functional components, hooks, react-dom, JSX, state, or even redux and all other subjects, etc. same same.
But of course, what's really important, is to find the way which fits you the best 😃
Well, let's not split hairs. Framework or component library - Ionic is really cool, and it makes it very easy to make cross platform apps. The reason I suggest that you learn React by itself first, is that you don't have to learn the APIs of Ionic at the same time.
But for sure - finding your own path is important ✌️
I understand your point better now, thx for the explanation. All cool 👍