sharing beta version app to somebody else

Good idea but

1.somebody has access to my account even it's a test account, he has to add watch to account etc.

2. It makes some trash from store (duplicates in apps).

It'll be more elegant when Garmin makes such rather simple functionality/tool for developers. Now I have to put into store new version every day/hour and confuse users.

_psx_ said:

1.somebody has access to my account even it's a test account, he has to add watch to account etc.

I think the idea for "Post the app with an unappealing or non-descriptive name under a different account and point users to it." is that you don't make it a beta app. It's just a different account so it doesn't get listed with the other apps in your existing dev account. (i.e. When you click on the dev's name, you can see all the apps from that dev.

So your users won't have to access your test account.

_psx_ said:

2. It makes some trash from store (duplicates in apps).

Yeah, this is a problem in general (aside from testing), as user sometimes request duplicate uploads for configurable data fields, for either of the 2 cases:

- Have different settings for the same data field

- Install the data field twice in the same activity (with different settings)

I have four versions of most of my data fields in the store.

I think a good middle-ground solution here would be to have apps which are only accessible by direct URL (like unlisted videos on youtube.) That way you could just send the URL to any interested testers.

Yes, it's the simplest.
I wrote about the user restriction that maybe Garmin will not want to spread the beta version.