Actually, I think if we were to "think outside of the box" it is actually possible to do what you would lke.
It will take a little bit of creativity, but essentially you will create a related table; lets call it photo position, to the asset feature class. This related table will contain a field for the asset photo description; enable a domain that contains the choices you commonly refer to “From top”, “From bottom”, “Overview” etc., and maybe a comment field.
Then the trick is to enable attachments for your related table' which gives you control over which photos are linked to which assets.
There you go, you can now relate your photos based on your categorization per asset. The post processing will take a join or two to assign the photo the correct name, but it is possible.
I use this method for a lot of our data collection and the collector app does support attachments for related tables; we use iOS devices, but it is supported within Andriod also. PLEASE keep in mind that currently user created relationships are based off of Global IDs; this is where you will need to be creative.
Let me know if you need more information.