oku-ui
Ionic || Capacitor Module v0.1.0
MVP Roadmap for Ionic Pergel Templates and Pergel Config 🔥
- [x] Capacitor Module https://github.com/oku-ui/pergel/pull/205
- [ ] Pergel Connect Capacitor Plugins @0fatihyildiz https://github.com/oku-ui/pergel/pull/215
- [x] Trapaze config API @productdevbook https://github.com/oku-ui/pergel/pull/207
- [ ] Docs write
- [ ] Splash Screen
- [ ] Onboarding
- [ ] Permission Access
- [ ] Presentation (Slider)
- [ ] Auth
- [ ] Sign in
- [ ] Sign Up
- [ ] Forgot Password
- [ ] OAuth (Google, Github)
- [ ] Home
- [ ] Settings
- [ ] Local Notification
- [ ] Cloud Notification
- [ ] RevenueCat
- [ ] Privacy Policy
- [ ] Terms of Usage
- [ ] Automatically Deploy CI CD
- [ ] Appstore
- [ ] Playstore
- [ ] Multi Themes
- [ ] Nuxt Ionic Pages
- [ ] Nuxt Ionic Helper Composables
- [ ] TailwindCSS Support
- [ ] Automatically Version Upgrade
- [ ] Deleting native configurations in plugins according to nuxt config
instead of going with ionic UI you can directly use the capacitor.js to scaffold the mobile responsive component and manage dynamic theme
instead of going with ionic UI you can directly use the capacitor.js to scaffold the mobile responsive component and manage dynamic theme
Yes We are also building a capacitor module. This way you will only activate the capacitor and use the module you want.
capacitor: true
instead of going with ionic UI you can directly use the capacitor.js to scaffold the mobile responsive component and manage dynamic theme
Yes We are also building a capacitor module. This way you will only activate the capacitor and use the module you want.
capacitor: true
how will you manage it with ssr. will there be option to separate out the nitro server api and the frontend on different sub domain so we can send code in capacitor builds
mobile app dont used ssr. ssr:false default. How do you plan to use SSR in the mobile app ?
mobile app dont used ssr.
ssr:falsedefault. How do you plan to use SSR in the mobile app ?
ssr is not possible in capacitor local build (sending code in build) but using directly with hosted domain but got issues around the native components as if call pwa components from plugin