You've listed exactly 3 points from a multipage document with dozens of requirements as if they summarize the whole document. This is not true - the requirements go way beyond the points you listed.
Apart from that, these points are merely necessary, but not sufficient for getting titles published. In a closed ecosystem you hand over control of your ability to publish to someone else, and that is fundamental. The terms that really matter in the MS developer agreement are:
> i. App Availability. Microsoft has no obligation to make any app available that you submit, even if that app is Certified
and
> j. Updates. Microsoft may update this agreement at any time in its sole discretion
That leaves open any kind of anticompetitive reason MS may come up with in the future to manipulate the store.
> 3.9 All app logic must originate from, and reside in, your app package
> 4.1.2 Your app must obtain opt-in or equivalent consent to share personal information
Did you even read any of those terms? They are ALL of the same nature.
> You've listed exactly 3 points from a multipage document with dozens of requirements as if they summarize the whole document. This is not true - the requirements go way beyond the points you listed.
Now you're just making things up.
> That leaves open any kind of anticompetitive reason MS may come up with in the future to manipulate the store.
Apart from that, these points are merely necessary, but not sufficient for getting titles published. In a closed ecosystem you hand over control of your ability to publish to someone else, and that is fundamental. The terms that really matter in the MS developer agreement are:
> i. App Availability. Microsoft has no obligation to make any app available that you submit, even if that app is Certified
and
> j. Updates. Microsoft may update this agreement at any time in its sole discretion
That leaves open any kind of anticompetitive reason MS may come up with in the future to manipulate the store.