<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 27/02/2014 20:00, Burr Sutter wrote:<br>
</div>
<blockquote
cite="mid:6FD9DE1E-C4F9-4A69-969F-DAFD5E4A2525@redhat.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
My quick feedback:
<div><br>
</div>
<div>The first screen should be the Message textarea, where I can
immediately hit Send Message/Finish (in the wizard) and ignore
the remaining steps - this would send the message to everybody,
across all variants, for my app that was selected prior to
seeing this screen.</div>
<div><br>
</div>
<div>At least, that is what the newbie needs - he only has 1 app,
1 variant, 1 installation/device token and he wishes to see if
the system works - if it fails, he reviews logs. :-)</div>
<div><br>
</div>
<div>Once the newbie has gotten his app created/debugged/tested,
it needs to roll-into production, where the average company is
likely to have 5 apps, 2 variants each and hundreds/thousands of
installations.</div>
<div><br>
</div>
</blockquote>
Where do you get these numbers from? That would be useful data to
have. ;)<br>
<br>
<br>
<blockquote
cite="mid:6FD9DE1E-C4F9-4A69-969F-DAFD5E4A2525@redhat.com"
type="cite">
<div>There will be another tier of users, who have dozens of apps,
with many variants, as they will likely use variants as "groups"
like</div>
<div>"Executive - iOS", "Executive - Android", "Sales Manager -
iOS", "Sales Manager - Android", "US Southeast Sales Team Member
- iOS", "US Southeast Sales Team Member - Android".</div>
<div><br>
</div>
<div>Was this last scenario envisioned for the use of variants?</div>
<div><br>
</div>
<div>And yes, there will be users who are supporting tens of
thousands of apps and variants and millions of
devices/installations - as they are hosting UPS like a
multi-tenant SaaS - but that is not exactly our target audience
in terms of UI design.</div>
<div><br>
</div>
</blockquote>
Yes, this is exactly why we have variants.<br>
<br>
I don't know about these numbers though. Use cases with millions of
variants need a different design. Variants are mostly there for us
for administrators to group things in a sensible way, having
millions of these will render that tool useless and we would have to
look for a different solution.<br>
<br>
Hylke<br>
</body>
</html>