<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<blockquote
cite="mid:CAAg5f2R+yN4aM0tKt=whz5RAShLpV2xO5-+HJmY666Yt=PkjmQ@mail.gmail.com"
type="cite">
<div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
<div>
<blockquote type="cite">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
<div>
<div><br>
</div>
<div>i was looking at this again and a question
popped into my head. Doesn't each variant need
there own certificate/google key. </div>
<div><br>
</div>
<div>So, for example, we have an "HR App", this
app has 3 variants</div>
<div><span style="white-space:pre-wrap"> </span>1.
free version</div>
<div><span style="white-space:pre-wrap"> </span>2.
paid version</div>
<div><span style="white-space:pre-wrap"> </span>3.
some other really cool version</div>
<div><br>
</div>
<div>i'm assuming that should be 3 different
certs/keys ( for development, another set for
prod ). i'm not sure the wireframes represent
this correctly</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>yes. the spec is indicating that!</div>
<div>Does the UI lead to confusion? </div>
</blockquote>
<div><br>
</div>
In it's current wireframe form yes. </div>
<div>
<br>
</div>
<div>But with this confirmation. we should be good going
forward</div>
<div>
<div><br>
</div>
<br>
</div>
</div>
</blockquote>
</div>
</blockquote>
<br>
I don't see this in the spec.<br>
Can you point me to the lines that mention this?<br>
<br>
Hylke<br>
<br>
</body>
</html>