as I understand it, it's not possible to write a SELinux policy for just one application, due to the simple fact that SELinux policies work on the basis of each file having a single tag.
so all policies that have to touch a file (or directory) have to agree on what tag to use for that file or directory.
this makes it impossible to ship a policy for your software, as you have to coordinate the tags with everything else on the system.
this is one of the things that I see as making AppArmor so much better in the real world. since it doesn't depend on global tags, but instead lists what files are allowed, the AA policy for a particular app really can be independent of the policy for all other apps. So it could be provided by the software developer.