Troubleshooting FlutterFlow for iOS App Store Upload and Enhancing App Presentation

The State Changers' meeting revolved around resolving issues related to app deployment, primarily on the iOS App Store, using FlutterFlow. A participant was struggling with the step requiring screenshots of their app on different devices for App Store submission. It was highlighted that screenshots uploaded to the App Store ought to be more than raw, literal screenshots. Instead, creative designs, which include certain elements from the app and some promotional text, generate client trust and sell better. Tools like Canva are recommended for this kind of work.

They talked about how raw screenshots might fulfill the submission requirement, but often fail to build audience trust. The participant was also educated on the fact that screenshots do not necessarily need to be from actual devices or emulators. They just need to correctly portray the user experience. Additionally, deploying the app for internal testing via the TestFlight app was suggested before submitting the app to the App Store. Enlisting someone with a device that isn’t readily available to test the app can help ensure usability across different devices. Sizes and orientations of devices were also considered as hurdles for app testing and development. Important keywords used during this discussion are iOS App Store, FlutterFlow, and emulator. Other tools mentioned include Canva and TestFlight but keywords like "Xano", "WeWeb", "Zapier", "Make", "Integromat", "Outseta", "Retool", "Bubble", "Adalo", "AppGyver", "AppSheet", "Comnoco", "Fastgen", "Firebase", "Google", "OAuth", "Stripe", "Twilio", "Airtable", "DraftBit", "Javascript", "Typescript", "React", "Vue.js", "JSX", "HTML", "CSS", "lambda", "serverless", "State Change", "ScriptTag", "OpenAI", "AI21" were not mentioned in this part of the transcript.

(Source: Office Hours 5/2 )

State Change Members Can View The Video Here

View This Video Now

Join State Change Risk-Free