If you have been pass the review process, could you please let me know via Like? I don't want you to go through the trouble of writing a comment.
Thank you. It's very encouraging😆
Or were you rejected? If so, I apologize for the inconvenience, but could you please let me know if it was for a FlutterFlow-specific reason? Also, it would be very helpful if you could tell how you were able to work around it.
The reason for this topic is as follows.
1. Accessibility of FlutterFlow App
FlutterFlow is responsive, but I am concerned about the lack of flexibility of the input widgets. For example, the dropdown below hides the bottom of the text because the height cannot be changed. (I think the width could be secured by wrapping the entire line and kicking the dropdown out to the next line)
At default scale
At larger scale
In my country, there was a discussion about third gender toilets. In the US, abortion is a major issue in the upcoming election. Excuse me, I don't want to get into a political debate here. I am trying to argue that it would not be at all surprising if the rights of people with handicaps to be able to use the app unimpeded increased rapidly. Past review trends are irrelevant. There are many apps that are given little or no consideration. But I don't want to be dismissed in a review for this reason.
If anyone rejects it for this reason, I will have to make a major redesign or give up using FlutterFlow because of this inescapable limitation.
Reference
This site, which is introduced at M3 site as Flutter example, displays input widgets very nicely, so I understand that it is a FlutterFlow limitation, not a Flutter limitation.
2. Bytecode matching issue
I searched this community by keyword of "Reject" and found the case that was rejected by Apple due to a bytecode match.
My understanding of Apple's guidelines is that they want to display apps with originality in their lineup. Suppose that there is an app generation service that advertises, "Just put your company logo here to create a social networking app". Apple don't want waste time to review for the apps, and they don't want fulfill their store by these type of apps.
I will create an app with originality, so there should be no problem. But since FlutterFlow provides the base layer, there will naturally be a lot of bytecode matches. While Apple can mechanically know how many bytecode matches in the code, they cannot know how much of the user experience that the app actually provides as its originality. This means that a certain amount of byte-matches might be smoothly rejected.
I would like to know how many rejects there are related to this, and how could you avoided. (In Dart, does replacing the name of the class "FFLocalizations" that found anywhere in my codes into another name chage bytecode?😜 )
Reference
3. As a knowledge for other FF users
If the app rejected, depending on the reason, a major modification may be necessary.
Therefore, you should always pay attention to the guidelines and the reasons for rejection while development. You can find many general reasons for rejection by googling, but not FlutterFlow-specific ones.
If there are FlutterFlow-specific trends, I would like to see them included in the FF knowledge base. That way, every FlutterFlow users can be aware of them and take the shortest route. I want to pick up information for this purpose.