Wrapply logoWrapply Tutorials
✅ Managed service

Managed publishing and Flutter customization with Wrapply

Wrapply can manage web-to-app conversion, Flutter source-code customization, Android and iOS build preparation, and store publishing support for clients who want a complete service.

What managed publishing means

Managed publishing means Wrapply helps you move from website or Flutter source code to store-ready app delivery. This can include conversion, app configuration, build preparation, source-code customization, APK/AAB generation, iOS support and submission guidance.

Managed conversion
Wrapply configures the web-to-app experience for your website, PWA, no-code or AI-generated web app.
Build preparation
APK, AAB and iOS build support depending on the selected service.
Source-code changes
Deeper Flutter customizations, integrations, navigation changes and native behavior can be handled as a service.
Store publishing support
Guidance and operational support for Google Play and App Store submission workflows.

When you need managed customization

The online builder covers fast customization such as AppBar, BottomNavigationBar and FloatingActionButton. More advanced changes require editing the Flutter source code.

Firebase integrations
Push notifications, analytics, authentication or Firestore logic.
Native permissions
Camera, location, file access, notifications and platform-specific behavior.
Custom navigation
Complex routing, protected areas, external link handling or payment flows.
Brand and UI changes
Custom screens, onboarding, splash, app-specific layouts and design refinements.

Updating code vs updating website content

This is one of the most important differences to understand after publishing.

Website content update
If you change text, pages, products, prices or layouts on the website URL loaded by the app, you usually update only the website.
Flutter code update
If you change app navigation, native configuration, Firebase, permissions, app icon, package name or source code logic, you must rebuild and republish.
Version update required
Before uploading a new Android/iOS build, update the version/build number in pubspec.yaml.
Store release required
After rebuilding, upload a new AAB to Google Play or a new iOS build to App Store Connect.
pubspec.yaml example:
version: 1.0.1+2

Android rebuild:
flutter build appbundle --release

iOS rebuild:
flutter build ipa --release

Managed publishing flow

Send your website URL

Wrapply reviews the website, PWA, no-code or AI-generated web app to understand the conversion needs.

Define output

Choose APK, AAB, Flutter source code, iOS support, managed publishing or custom integration work.

Prepare app configuration

Set app name, icon, AppBar, BottomNavigationBar, FAB, package name and publishing metadata.

Build and test

Wrapply prepares files, tests the main flow and checks key app behavior.

Publish or deliver

Files are delivered or publishing support is provided for Google Play/App Store workflows.

What the client should prepare

Website URL
The final URL that the mobile app should load.
App name and icon
Final brand name and high-resolution app icon.
Store accounts
Google Play Console and Apple Developer/App Store Connect access if publishing is required.
Privacy policy
Required for many publishing workflows, especially if the app collects user data.
Screenshots and description
Store listing content for Google Play and App Store.
Feature requirements
Any custom Flutter, Firebase, native or publishing requirements.

FAQ

Can Wrapply modify the Flutter source code?

Yes. Source-code customization can be requested for integrations, navigation, Firebase, native behavior and UI changes.

Do I need a new app build for every website update?

No. If you only update website content at the URL loaded by the app, you usually do not need a new app build.

When do I need to update pubspec.yaml?

When you rebuild and submit a new app version to Google Play or App Store, update the version/build number in pubspec.yaml.