Hi Norman,
I suppose you are referring to writing NDEF messages? When writing one, the tag reader will try to overwrite the first NDEF message it has found when the tag was tapped.
So: if your tag contains a capability container followed by a bunch of non-NDEF TLVs (such as lock and proprietary), and then on page X onwards its NDEF TLV, that page X will be the page to write. This is the behavior when using the high-level API on Android or iOS. I assume the NXP App Tag Info uses the same approach, whether it uses the high-level or the low-level API (I don't know which).
If you want to deviate from that behavior you'll need to use the low-level APIs offered by Android and iOS, i.e. you'll need to write each and every NFC page yourself, in the correct way.
Aside: there also exist mobile APPs which allow you to write any content in any NFC page. One I know but lack a lot of experience with is the iOS APP "Smart NFC".
Kind regards,
Dries.