[V1] how to build with ios theme? -T ios



  • [V1] How do I build/run (cordova)apps with ios theme?

    From the V1 doc:
    https://v1.quasar-framework.org/quasar-cli/developing-mobile-apps/build-commands

    quasar dev -m cordova -T ios
    quasar build -m cordova -T ios

    these commands result in a app with Material Android look/theme instead of ios.

    This used to work in v0.17x


  • Admin

    The iOS theme is no longer available, BUT as you will see, it’s also not necessary anymore:

    • There are examples in the docs of how to make different components look and feel like iOS
    • You can hook into $q.platform.is.ios to help you in setting component props differently
    • The new components are very easy to customize (much easier than in Legacy Quasar)


  • so if I understand correctly , Quasar V1 does not support IOS apps anymore ‘out of the box’. I say this because I am under the impression( and correct me if i am wrong) that the Apple Itunes app review team rejects any apps that have an Android look and feel. Is this correct?



  • There is nothing in the review guide that says the app’s design has to follow iOS design guidelines.

    Scott



  • @rstoenescu
    Quasar looks more and more like vuetify. Material Design Component Framework with Vuejs
    Give me a good reason to stay with Quasar



  • Quasar has a lot more to offer (CLI, extensions, better app structure, better components, PWA SPA Cordova Electron)



  • @Marc - looks can be deceiving. As @lucasfernog mentioned, above and beyond the many extra components you have available, Quasar also is built a few steps further and better than Vuetify.

    Quasar is built for and around an ecosystem of developer tools. It starts with the CLI and the ability to take a singular code base and build it out to multiple app types, SPA, PWA, PWA + SSR, Cordova hybrids and Electron apps. Quasar will have IDE support for IntelliJ and VSCode (IntelliJ is practically finished). It will be TS driven in the future. The extension system, once it catches on, means devs like you will be able to share added features and components. We’ll have some official extensions too, like the QMediaPlayer extension (which is also practically finished) and more extensions from a list of 26 we’ve came up with currently. Not all of them will be official extensions, but you can see we are thinking much more about the future - your future. 😄

    Scott



  • @s-molinari
    Today, I have to start a new project. I have 3 solutions v0.17 (end of life), v1 (in beta) and vuetify.What is the best solution? I’m very familiar with v0.17 and now I have to learn V1 or Vuetify and I think Vuetify’s API will remain stable.



  • That is a tough choice. @Marc

    If v1’s API changes, it will be only minimal, which means relatively easy upgrading for you. I think with the new docs, if you are an advanced or even intermediate JS and Vue dev, you’ll get rolling along rather quickly. If you knew v0.17 and how to work with it, v1.0 is fairly the same overall from a CLI/ dev experience perspective. We also have an upgrade guide coming out like any day now (I believe with beta 5), which will also help you a lot to see the differences between 0.17 and 1.0 components and other changes.

    The development on v1.0 is also rapidly ongoing. I know. That can be a good thing, but also a bad thing. Depends on how you look at it. I look at it as a great thing. 😁

    Also, what type of app, or even apps, will your project need to be? That might also help you with your decision?

    Scott



  • @Marc i would go with v1-beta, its solid and pretty neat.

    quasar offers the best components i have seen in the the vuejs eco system so far.



  • @rstoenescu

    Where can I find the examples to make components look and feel like iOS?

    Are there any plans of any kind of (offical) ios theme support for standard components in V1 in the near future?



  • @s-molinari Can we follow the work you guys are doing on these extensions? Or at least the list of them… I am thinking about making some of my own after the QMediaPlayer extension release, and I think it would be useless to work on something the Quasar team are already doing

    Also, I really like to follow this project



  • @lucasfernog - I’m not sure the list of extensions we gathered is for the public yet. I’ll check. You could also mention your first few ideas here and I could tell you if they were already mentioned or not. And to be honest, unless it is going to be an official extension, which not too many will be, you can start doing one or two on your own. There are no “dibs” on extensions from the Quasar team. It will be a free and open market for them. That’s one of the beauties of them. 😁

    Scott



  • @lucasfernog - Please DM me to further discuss extension work. Thanks!

    Scott



  • Not wanting to insult people but I have the feeling this thread is diverting from the original topic: what happened to the IOS theme support in V1.

    Fact is that one of the main features(out of the box ios theming) has been been removed from Quasar [V1] and replaced by: do it yourself. While (ios) theming is ‘advertised’ as one of the main features of the quasar framework:

    https://quasar-framework.org/

    • Hybrid Mobile Apps (that look native!)*

    https://www.patreon.com/quasarframework

    • Two Themes (more to come) - Material theme and iOS theme.*
    • native mobile Apps (that really look native!)*

    Could anyone tell me if there are plans of any kind of (offical) ios theme support for in V1 in the near future?


  • Admin

    @dobbel

    We’ve decided not to support two versions of themes to better concentrate on getting just the one right. This however does not mean that your apps will look wrong on iOS or that real themes won’t be available in the future. Quite the contrary.

    Let’s be honest, the iOS theme was not really following the iOS guidelines and there were too few components having different behavior based on the theming. But as few as they were, the development doubled (even tripled in some cases) because basically Quasar was a two frameworks in one – and having in mind the current level of funding, this cannot work long-term due to the continuous exhaustion levels.

    We are also planning on a real theming system in the near future, which is part of the grand scheme of things with v1, where themes can be exported and shared among the community. We strived a lot to make v1 be extremely easy to customize which fits extremely well with these plans. This could never have been possible with two base themes because the CSS would have been a complete mess.

    We also asked our Patrons on this matter and the majority ruled that it would be better to focus on better components and faster releases.

    This was a high overview / satellite view of how and why things changed (to the better!). When getting into details, it will become very obvious why there’s no need for two base themes on Quasar. Take QToolbar for example. It’s way easier for the developer to make it look differently on an Android and iOS (look at v1 docs examples, takes about 15 seconds to differentiate the design if you want). Maybe some don’t even want to be forced into changing the design of Toolbar for iOS specifically. Dealing with the color, inverted-color etc props was very hard to grasp by many. We learned from that and this one base theme allows for a lot more logical props and behavior. It all becomes like a breeze in v1 while developing, which is our main task when creating Quasar. Sometimes you have to take a couple of steps back to take better steps forward.

    This one base theme and the multiple real themes coming in the near future is a big step forward. If it’s not yet clear now, it will be very obvious quite soon as we approach final 1.0 build.



  • @s-molinari
    Thank you for your reply. My decision was made when I read the upgrade documentation.
    New projects will be with Vuetify. I have applications in version 0.14 and others in version 0.17 and it is sometimes difficult to switch from one to another. Three versions would be more complicated than learning a new framework.
    I think the Vuetify API is more stable.
    Why rename ‘plugin’ in ‘boot’? q.i18n to lang ?, tertiary color to accentuate? … and so on.
    To avoid confusion, all components should have been renamed, such as QInput to NInput.


  • Admin

    @Marc

    Switching to another framework just when Quasar’s API becomes stable? 🙂



  • @rstoenescu said in [V1] how to build with ios theme? -T ios:

    @Marc

    Switching to another framework just when Quasar’s API becomes stable? 🙂

    well it’s a valid choice since he need two themes. unless he wants to continue with 0.17 which won’t be updated much now that v1 is out.



  • @dobbel said in [V1] how to build with ios theme? -T ios:

    @rstoenescu

    Where can I find the examples to make components look and feel like iOS?

    Are there any plans of any kind of (offical) ios theme support for standard components in V1 in the near future?

    Still no answer on this. We were creating a SPA with iOS theme, converting to v1 completely broke our design. Can we import old ios stylings manualy somehow?


Log in to reply