What I mean is that I would like to be able to execute ALL cordova related commands (including and referring specifically to “simulate” which is the thing I use the most while developing)
As per today it looks to me that
either you avoid those commands
or you must work in the cordova directory
but that’s explicitly mentioned as a bad practice in F7 projects…
So it makes me assume that some automatisms will not work if I have an F7 project but I’m working in the cordova dir (specifically it seems that “routing” could not be automated properly).
NOTE: I’m not expert in F7 v5, just learning now, so I understand my points might be trivial but at the same time, my learning experience could be useful to improve documentation/processes for all newcomers…
@Erik_Cornelisse@tiptronic i am totally agree that something like Best practise/Most common errors/Etc. is missing. But help me to figure out what is exactly missing I raised the old topic that was forgot for some reason: Let’s make FAQ section Would be cool if you can add there your thoughts, anything that comes to your mind
Also, guys, if you see something is missing in docs, don’t hesitate to raise an issue at Framework7 Website repo at https://github.com/framework7io/framework7-website/ or if you can, you can edit docs directly and send the PR. I will really appreciate it
is there any chance adding custom components like vue ?
import mycompoenet from './mycomponent'
…
{
components: [‘mycomponent’]
}
…
i know there is registerComponent but it’s before init,
it would be great if we could use it afterwards and on demand like using import(’’) inside components;
Smaller bundle size. Since V1 it has not stopped growing, even the minimal setup without components. In Android this has a big impact on the startup time of the app. For many apps may not be a problem for for apps made to be opened several times a day, it can be frustrating.
Yes, on PWAs it can bet cached and on Cordova apps, it is loaded locally so it should be fast. But the fact is that a few hundreds of KB can make a huge difference on the boot time of an app on low-end Android devices, even when everything is at local storage or cached.
Imagine opening an app multiple times a day just to log tasks and every time you have to wait 4-5 seconds on the splash screen… If you reduce the bundle size, the same app can be opened in 1/2 seconds less depending on the device. This makes a huge impact on the user experience, even more than a fancy app with tons of beautiful components.
For example, my Framework 7 V1 js bundle is 247 KB with all this components:
I support this idea pretty much.
Caching is not a solution, because caching happens too late.
E.g. if you’re on a 3G network, inital loading times are crucial - and the (sad) truth is, that 3G (or to some extent even EDGE) is still a big deal in big parts of the world.
Documentation on how to use Framework7 for server side rendering would be better. Perhaps, some plugins or startup code to use with NUXT, others SSG such as VuePress, Gridsome would be great.
Сейчас много разработчиков из России активно начинают использовать ф7 для VK mini apps. Было бы здорово, если бы появился адаптированный ф7 шаблон под vkui.
I raised the old topic that was forgot for some reason: 
