Repeated 2.3.1(a) + 4.2 rejection after adding more native features

Hi,

My app LiveShift passed review in its first two versions without this issue. After that, I added more native functionality, including a monthly calendar with shift templates, but now the app keeps getting rejected under Guideline 2.3.1(a) and 4.2.

The rejection says the app has hidden features and feels similar to a web browsing experience. That’s confusing to me because the app is fully native, has no webview or embedded website, and all features are available through the main tabs: Home, Calendar, Shifts, and Settings.

The app includes real-time shift tracking, Live Activities / Dynamic Island, shift history, overtime and extra pay rules, notifications, export, and now Calendar planning.

Has anyone had this happen after adding more features? Would better Review Notes, a demo video, or an appeal be the best next step?

Repeated 2.3.1(a) + 4.2 rejection after adding more native features
 
 
Q