MeetAir is complete video meeting system to easily start your online meeting platform.Is have most powerful admin panel for manage meeting, history, notification, analytics, app configuration and many more.MeetAir was built with one of the best mobile development systems — Flutter. The app is compatible with both Android and iOS systems.
We recommend using the latest Android Studio And Flutter SDK, which can be downloaded from here: Android Studio, Flutter SDK, Cocoapods
Recommended Version
Android Studio Installation(Windows)
Android Studio Installation(Mac)
If you have updated you mac to Catalina from mojavi or earlier version then you may fetch some issues.Please follow bellow video to fix it.
config.dart
file.List » introContent
.done!
Create a project
or Add Project
.continue
to redirect project dashboard.Android
Android Icon
Then enter Android Package Name, App Name
and click on register app
.google-services.json
file and copy/paste it to android studio project directory.Location:: project » android » app
.Done!
Note:Android package name should be the remain same with your studio project else build will not be work.
iOS
iOS Icon
Then enter iOS bundle ID, App Name
and click on register app
.GoogleService-Info.plist
file and copy/paste it to android studio project directory.Location:: project » ios » Runner
.Done!
Note:iOS Bundle ID should be the remain same with your studio project else build will not be work.
Android
Create Project
.Continue
.Cloud Messaging
App ID
and Paste to Android Studio Projectconfig.dart
.Check subscriber
on OneSignal you will see success Notification.Done!
iOS
iOS Icon
Then select .p12 certificate from your computer.App ID
and Paste to Android Studio Projectconfig.dart
.if you have done it by android setup then just skip this step.Check subscriber
on OneSignal you will see success Notification.Done!
You have to create Firebase project first see tutorial if you did not created yet.
Video Tutorial::
OR follow bellow step::
You have to create Firebase project first see tutorial if you did not created yet.
Video Tutorial::
OR follow bellow step::
You have to create Firebase project first see tutorial if you did not created yet.
Video Tutorial::
OR follow bellow step::
You have to create Firebase project first see tutorial if you did not created yet.
Video Tutorial::
OR follow bellow step::
Note: Phone login will not be work on emulation.So please test it on real device.
Note: Phone login will not be work on emulation.So please test it on real device.
Apple login is available for iOS only.
Last step you have to add your PC's SHA-Certificate to Firebase
Generate SHA-Certificate Fingerprint by below command
MAC:: keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android
Windows:: keytool -list -v -keystore "\.android\debug.keystore" -alias androiddebugkey -storepass android -keypass android
Add SHA-Certificate Fingerprint to Firebase
Note: You have to use Google Play App sign in certificate instead of PC's for release version.
Setting » API Setting
enter information like on the image below:API SERVER URL
from Admin panel and paste it to config.dart
file.API KEY
from Admin panel and paste it to config.dart
file.Project » assets » images » common
390x222
.Project » assets » images
512x512
.AndroidManifest.xml
from Project » android » app » src » main
.MeetAir
AndroidManifest.xml
from Project » android » app » src » main
.com.spagreen.meetair
Note: you have to complete Firebase setup with same package name first.
Project » assets » images
512x512
.flutter build apk --debug
key.jks
file to Project » keys » key.jks
flutter build apk
This step covers reviewing the most important settings in the Xcode workspace. For detailed procedures and descriptions, see Prepare for app distribution.
Navigate to your target’s settings in Xcode:
Runner.xcworkspace
in your app’s
ios
folder.
Verify the most important settings.
In the Identity section:
Display Name
Bundle Identifier
In the Signing & Capabilities section:
Automatically manage signing
true
by default, which should
be sufficient for most apps. For more complex scenarios,
see the
Code Signing Guide.
Team
In the Deployment Info section:
Deployment Target:
The General tab of your project settings should resemble the following:
For a detailed overview of app signing, see Create, export, and delete signing certificates.
In the main view sidebar, select the
Info.plist
file.
Rename the
Bundle name field.
The default version number of the app is
1.0.0
.
To update it, navigate to the
pubspec.yaml
file
and update the following line:
version: 1.0.0+1
The version number is three numbers separated by dots,
such as
1.0.0
in the example above, followed by an optional
build number such as
1
in the example above, separated by a
+
.
Both the version and the build number may be overridden in Flutter’s
build by specifying
--build-name
and
--build-number
,
respectively.
In iOS,
build-name
uses
CFBundleShortVersionString
while
build-number
uses
CFBundleVersion
.
Read more about iOS versioning at
Core Foundation Keys
on the Apple Developer’s site.
When a new Flutter app is created, a placeholder icon set is created. This step covers replacing these placeholder icons with your app’s icons:
Assets.xcassets
in the
Runner
folder. Update the placeholder icons with your own app icons.
flutter run
.
This step covers creating a build archive and uploading your build to App Store Connect.
During development, you’ve been building, debugging, and testing with debug builds. When you’re ready to ship your app to users on the App Store or TestFlight, you need to prepare a release build. At this point, you might consider obfuscating your Dart code to make it more difficult to reverse engineer. Obfuscating your code involves adding a couple flags to your build command.
On the command line, follow these steps in your application directory:
flutter build ios
to create a release build
(
flutter build
defaults to
--release
).
In Xcode, configure the app version and build:
Runner.xcworkspace
in your app’s
ios
folder.
Finally, create a build archive and upload it to App Store Connect:
You should receive an email within 30 minutes notifying you that your build has been validated and is available to release to testers on TestFlight. At this point you can choose whether to release on TestFlight, or go ahead and release your app to the App Store.
For more details, see Upload an app to App Store Connect.
TestFlight allows developers to push their apps to internal and external testers. This optional step covers releasing your build on TestFlight.
For more details, see Distribute an app using TestFlight.
When you’re ready to release your app to the world, follow these steps to submit your app for review and release to the App Store:
Apple notifies you when their app review process is complete. Your app is released according to the instructions you specified in the Version Release section.
For more details, see Distribute an app through the App Store.
The Distribute your app guide provides a detailed overview of the process of releasing an app to the App Store.
You need a license code.Buy it from Envato market.