Comment by Cloudef
2 years ago
Interesting. One thing I don't like about flutter is the management of platform specific meta files. How does skip handle this? Do I still have to write bunch of .manifest, res and .plist files per platform? How about screenshot and all the other crap appstore and playstore wants?
The flutter projects usually start clean, but then these platform specific hacks start to pile up and it's ugly and annoying to update to later flutter skeleton.
While the core of your Skip code and resources exists in one or more Swift Package Manager module (which will be transpiled into corresponding Gradle modules), the scaffolding of your actual app is still an Xcode project on the iOS side, and an Android Studio/Gradle project on the Android side.
When you create a new project with `skip init`, it will create the two projects for you, along with fastlane configurations for each of the projects. From there, you'll proceed with all the deployment-specific stuff (screenshots, preview videos, metadata, content ratings, etc.) as per each individual store's guidelines.
Each side of the project is always an individually valid project, following the corresponding platform's recommended conventions. There aren't any bespoke plist formats or any Skip-specific manifests to deal with, with the exception of one small central "Skip.env" file, that contains basic shared information like the app name and version number.