status-im/slack-archive
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Files
master
slack-archive/26-beta.html
T

569 lines
163 KiB
HTML
Raw Permalink Blame History

<html><body><style>
* {
font-family:sans-serif;
}
body {
text-align:center;
padding:1em;
}
.messages {
width:100%;
max-width:700px;
text-align:left;
display:inline-block;
}
.messages img {
background-color:rgb(248,244,240);
width:36px;
height:36px;
border-radius:0.2em;
display:inline-block;
vertical-align:top;
margin-right:0.65em;
}
.messages .time {
display:inline-block;
color:rgb(200,200,200);
margin-left:0.5em;
}
.messages .username {
display:inline-block;
font-weight:600;
line-height:1;
}
.messages .message {
display:inline-block;
vertical-align:top;
line-height:1;
width:calc(100% - 3em);
}
.messages .message .msg {
line-height:1.5;
}
</style><div class="messages"><div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 10:25</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-14 11:30</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2017-12-14 12:22</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-01-09/125597416918_4b7b095b4e695e7a8be1_72.jpg" /><div class="message"><div class="username">carl</div><div class="time">2017-12-14 12:22</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/9a90059210aaacfa5550a12d39020469.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0022-72.png" /><div class="message"><div class="username">jeka</div><div class="time">2017-12-14 12:22</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2017-12-14 12:34</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-08-27/423671855091_1b4f90cfbdd6a3ee2b6f_72.jpg" /><div class="message"><div class="username">roman</div><div class="time">2017-12-14 12:34</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-07/208536923616_b5117c2515a2b7efe2a4_72.jpg" /><div class="message"><div class="username">tiabc</div><div class="time">2017-12-14 12:34</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-11-15/272576481349_8a10b77047c084ffde3c_72.png" /><div class="message"><div class="username">james884</div><div class="time">2017-12-14 12:34</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/b11645e09683360c0849df16c77e9980.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">themue</div><div class="time">2017-12-14 12:34</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2017-12-14 12:34</div><div class="msg">The prototype <a href="https://invis.io/KXEWN9XHM#/269041131_Onboarding1">https://invis.io/KXEWN9XHM#/269041131_Onboarding1</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2017-12-14 12:34</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2017-12-14 12:34</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/a5f396eba057f6f6ce181fd462ff2b1a.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0025-72.png" /><div class="message"><div class="username">goranjovic</div><div class="time">2017-12-14 12:34</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 12:35</div><div class="msg">Also <a href="https://docs.google.com/document/d/1PiEU3xIrjMw4DvHQ_0eMdyj3lSkBona_0-6zM-qb5aQ/edit">https://docs.google.com/document/d/1PiEU3xIrjMw4DvHQ_0eMdyj3lSkBona_0-6zM-qb5aQ/edit</a></div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-14 12:35</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-09-12/240066984213_b35ca6f6b9658bf5cabb_72.jpg" /><div class="message"><div class="username">jonny.z</div><div class="time">2017-12-14 12:35</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 12:35</div><div class="msg">It reviews the current alpha screens and features and compares it to a simplified MVP</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2017-12-14 12:36</div><div class="msg">What?s your preferred way to get feedback? Comments in Invision or here?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-24/320320314756_fe0f3ce0bb820f1aa8e3_72.jpg" /><div class="message"><div class="username">dmitryn</div><div class="time">2017-12-14 12:36</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-14 12:36</div><div class="msg">do you think we can add screens to google doc?</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/fcc4675bd0ade27de9baefb82098e500.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0002-72.png" /><div class="message"><div class="username">yenda</div><div class="time">2017-12-14 12:36</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-14 12:36</div><div class="msg">visual reference and easier to comment on specifics there</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 12:37</div><div class="msg">Any/all</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 12:37</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2017-12-14 12:44</div><div class="msg">I think it's a really great step towards MVP! Much easier to navigate and explore the app. I could easily explain my non-tech friends what?s going on here. (1) Descriptions displayed on the first screen and during account creation are not really explaining what?s going on but I guess they will be updated. (2) Why the first tab is `Home` instead of `Chat`, which would kinda follow the pattern?</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-14 12:46</div><div class="msg">Or `browse`. `Home` sounds like `default`</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 12:48</div><div class="msg">Thanks for the feedback!
Some replies:
1) Descriptions are placeholder for now. We want to give the user some context, but not get in their way.
2) Didn?t go with `chat` since it has Dapps. Other suggestions could be `tabs` or the ones you suggested. WIP!</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2017-12-14 12:50</div><div class="msg">Cool! Way to go, team!</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 13:24</div><div class="msg">After diving deep into the MVP and screens, it seems like we are really close from a users point of view. We have all the pieces in the app, and just need to massage these into a good and polished spot.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 13:25</div><div class="msg">And once we have a MVP release candidate we can really open it up for testers and surface any big performance, technical, or usability shortcomings.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2017-12-14 13:28</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 13:45</div><div class="msg">question: how do assets work in the wallet? Can one wallet have multiple assets? Or are assets intended to be separate wallets?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 13:45</div><div class="msg">referring to this screen <a href="https://projects.invisionapp.com/share/KXEWN9XHM#/screens/268743893">https://projects.invisionapp.com/share/KXEWN9XHM#/screens/268743893</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 13:45</div><div class="msg">@chad set the channel topic: <a href="https://invis.io/KXEWN9XHM#/269041131_Onboarding1">https://invis.io/KXEWN9XHM#/269041131_Onboarding1</a></div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-14 13:46</div><div class="msg">We don't intend to support multiple wallet</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-14 13:47</div><div class="msg">A wallet is tied to an ethereum address</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-14 13:47</div><div class="msg">Tokens are just attributes of an address</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-14 13:47</div><div class="msg">Assets in our case are ethereum + tokens you have selected to be visible</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 13:49</div><div class="msg">Where can I learn more about this?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2017-12-14 13:53</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-14 13:55</div><div class="msg">Some of this is ethereum concepts (address, erc20 tokens). Some is semantic we have adopted (assets, wallet is pretty common)</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-14 13:55</div><div class="msg">No very well defined in general.</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-14 13:56</div><div class="msg">Which part precisely you would want detailed?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 13:58</div><div class="msg">My point of reference is coinbase, so anything that differs from that, particularly around tokens.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 13:58</div><div class="msg">What does @browse do in the context of p2p chats?</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-14 13:59</div><div class="msg">ERC20 is a smart contract standard than defines abstract `tokens` transfers. It is what `SNT` is based on.</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-14 14:00</div><div class="msg">It's been popular lately and one of the driver of ICOs.</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-14 14:00</div><div class="msg"><a href="https://github.com/ethereum/EIPs/blob/master/EIPS/eip-20-token-standard.md">https://github.com/ethereum/EIPs/blob/master/EIPS/eip-20-token-standard.md</a> for much more details.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 14:00</div><div class="msg">Thank you!</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-14 14:00</div><div class="msg">Most tokens follow this standard that's why they are supported by plenty exchanges</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/a5f396eba057f6f6ce181fd462ff2b1a.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0025-72.png" /><div class="message"><div class="username">goranjovic</div><div class="time">2017-12-14 14:01</div><div class="msg">Nothing related to the chat. It just lets you browse the web, or use dapps by url.</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-14 14:01</div><div class="msg">In status, `assets` is a bunch of stuff worth value associated to your wallet (currently ethereum and erc20 tokens). There could be others (cryptokitties for instance)</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 14:02</div><div class="msg">Doing it from within a p2p chat implies that I?m interacting with someone. (such as sending a file, or transferring funds). I wonder what relevance it has here?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 14:04</div><div class="msg">Super informative! Is it needed for core wallet functionality? Part of the MVP or something we add later?</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/a5f396eba057f6f6ce181fd462ff2b1a.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0025-72.png" /><div class="message"><div class="username">goranjovic</div><div class="time">2017-12-14 14:04</div><div class="msg">I agree. This was brought up in discussions, with more or less this conclusion. I don't know if we ever documented it anywhere, though.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2017-12-14 14:05</div><div class="msg">At least we should support our SNT token</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-14 14:08</div><div class="msg">I think it is a nice feature, SNT is probably a must.</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-14 14:08</div><div class="msg">Others are not very useful as long as we don't support multiple wallet.</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-14 14:09</div><div class="msg">Also note it's already implemented :slightly_smiling_face:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 14:09</div><div class="msg">Not in the alpha? is it in the internal releases?</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-14 14:11</div><div class="msg">Right I mean it's in develop</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/a5f396eba057f6f6ce181fd462ff2b1a.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0025-72.png" /><div class="message"><div class="username">goranjovic</div><div class="time">2017-12-14 14:16</div><div class="msg">Hm, actually now that I think about it, `@browse` is probably there because of dapps with which you can also interact by chatting. This is how old Wallet used to work for example - you'd open a chat with a dapp and then you could either interact through the web view or by sending text messages.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 14:17</div><div class="msg">When I click a Dapp from the chat list the Browser window just opens automatically</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 14:17</div><div class="msg">So maybe this is a system function instead of a user function?</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/a5f396eba057f6f6ce181fd462ff2b1a.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0025-72.png" /><div class="message"><div class="username">goranjovic</div><div class="time">2017-12-14 14:17</div><div class="msg">Yes and if you close it you can chat with it.</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/a5f396eba057f6f6ce181fd462ff2b1a.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0025-72.png" /><div class="message"><div class="username">goranjovic</div><div class="time">2017-12-14 14:17</div><div class="msg">But then you need a way to open the browser again - that's @browse</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 14:17</div><div class="msg">hmmm</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/a5f396eba057f6f6ce181fd462ff2b1a.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0025-72.png" /><div class="message"><div class="username">goranjovic</div><div class="time">2017-12-14 14:18</div><div class="msg">TBH, it makes more sense to reverse that.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 14:18</div><div class="msg">so some dapps can be both chatted with and browsed?</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/a5f396eba057f6f6ce181fd462ff2b1a.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0025-72.png" /><div class="message"><div class="username">goranjovic</div><div class="time">2017-12-14 14:18</div><div class="msg">i.e. to nest the "chat" option to the web view, rather than the other way</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/a5f396eba057f6f6ce181fd462ff2b1a.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0025-72.png" /><div class="message"><div class="username">goranjovic</div><div class="time">2017-12-14 14:19</div><div class="msg">Right now, I don't think there are any. There used to be one - old Wallet.</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/a5f396eba057f6f6ce181fd462ff2b1a.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0025-72.png" /><div class="message"><div class="username">goranjovic</div><div class="time">2017-12-14 14:19</div><div class="msg">It was our internal dapp, retired now. Completely replaced by what you see now in Wallet tab.</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/a5f396eba057f6f6ce181fd462ff2b1a.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0025-72.png" /><div class="message"><div class="username">goranjovic</div><div class="time">2017-12-14 14:27</div><div class="msg">So to clarify, all dapps need @browse, but very few if any also support chat, as of this moment.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 17:58</div><div class="msg">:thinking_face: In that case maybe we should remove browse from chat, and remove chat from dapps?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 17:59</div><div class="msg">It is weird to close a dapp window and end up on chat. similarly it is weird to open a browser from chat</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 18:02</div><div class="msg">@jonny.z Any ideas on what we should put into the welcome message here? <a href="https://projects.invisionapp.com/share/KXEWN9XHM#/screens/269041164">https://projects.invisionapp.com/share/KXEWN9XHM#/screens/269041164</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 18:03</div><div class="msg">How can we educate, inform, and inspire here about the app and ethereum?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-09-12/240066984213_b35ca6f6b9658bf5cabb_72.jpg" /><div class="message"><div class="username">jonny.z</div><div class="time">2017-12-14 18:04</div><div class="msg">great question - ill write up something today and send it over. Will be placeholder for now while we define our tone and lead message. Cool?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 18:06</div><div class="msg">Cool. In the next week or so I'll write up a GH issue we can track it. We can start simple for the MVP and expand messaging/help/onboarding as we grow.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-09-12/240066984213_b35ca6f6b9658bf5cabb_72.jpg" /><div class="message"><div class="username">jonny.z</div><div class="time">2017-12-14 18:09</div><div class="msg">perfect</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 18:37</div><div class="msg">Everyone, thanks for the feedback so far. Main discussions so far were around SNT in the MVP and public/group chats. Seems like we are all generally on the same page :slightly_smiling_face:. If there are some strong opinions/ideas about taking a different approach please comment in a thread here, or PM me.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 21:14</div><div class="msg"><a href="https://github.com/status-im/ideas/issues/61">https://github.com/status-im/ideas/issues/61</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 21:17</div><div class="msg">The app structure refinement and UI update seems one of the most agreed upon aspect of the beta tweaks and seems a great candidate to get started. I added a bit more context to this idea GH issue. I'd appreciate any feedback as well as contributors. Who wants to join @andmironov and me on this and get on the road to beta!?!?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 21:35</div><div class="msg">@chad is MVP doc is what written in <a href="https://github.com/status-im/ideas/issues/26">https://github.com/status-im/ideas/issues/26</a> ? I?m reading GH content and don't see anything in the MVP doc about performance for example. I see only feature comparison. Is it just a part of idea 26 or how should I look at the doc?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 21:36</div><div class="msg">I also would really appreciate if MVP will be explained from the goals perspective. So all decisions can be based on ?do we achieve the goal or not?. Now, GH content gives me an idea on the goals `For the Beta we should aim to have a working, stable foundational client, that we are using on a daily basis, even to coordinate our development.` while MVP doc does not.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 21:38</div><div class="msg">So, decision to remove group chat for example would be ?no go? if I rely on the goal, as we would not be able to use it to coordinate development without group chats. wdyt?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 21:45</div><div class="msg">if we want user base to grow as soon as possible (like also can be one of the goals) then wouldn't discover even in its current form be beneficial, so user can see at least ?friends of friends? and their statuses and add them? Again - having the goal in mind would simplify the judgement on do we need discover or not</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 21:47</div><div class="msg">I would say - in beta I want 1. users to feel safe for their funds (ETH and SNT) and be able to use them in Mainnet 2. Be able to browse and use DApps and have Status as main tool to do this 3. Communicate with other users by sending messages and funds (also in safe manner, so fishing or anything that can put user in trouble should be fixed/removed)</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2017-12-14 21:47</div><div class="msg">My 2c - Discover is an important feature, and I think it provides value. In its current form, its confusing and to improve integration with the DApps will require a lot of work. The 'friends of friends' feature, is also great, but not something that needs to be in a MVP that shows the basic functionality of the app</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2017-12-14 21:48</div><div class="msg">They can still access DApps by entering a URL on the "Home" screen.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 21:48</div><div class="msg">again having Goals for MVP simplifies exchaning opinions and shifts battles to - how we can get to this point</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 21:50</div><div class="msg">I?m trying to demo how sharing the Goals instead of feature list can help to organise features and make decisions, it can be other list - but having the goals is something like ?where we would like to be? rather then ?which road do we take to get there?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2017-12-14 21:52</div><div class="msg">Good point. imo - the Goals of the MVP should be to:
(a) Demonstrate a intuitive UX for the core Status elements, Chat, Wallet and DApp access
(b) Deliver (a), without performance issues.
(c) Create a simple onboarding experience for our users.
All the goals can/should be measured with success metrics
I'd be curious to hear other people's opinions on this, and whether @chad has it documented already maybe</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 21:54</div><div class="msg">Good summary Nabil.
Haven't documented anything yet, and need to update idea#26. Right now I'm gathering context, feeling out the team and sprinkling in some first impressions. Starting broad strokes in pencil before firming it up.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-14 21:56</div><div class="msg">@anna yep good point. I'd like to have a heuristic that enables anyone to easily answer if/when a feature is needed.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 21:56</div><div class="msg">so we can demonstrate UX in testnet and consider we are done, right? :slightly_smiling_face:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 21:57</div><div class="msg">sorry will be on that provocative side to get real needs</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 21:57</div><div class="msg">we think that onboarding is not intuitive - why? can we test the new onboarding and other UX elements now and check if they are as intuitive as we think?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 21:57</div><div class="msg">without implementing them</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 21:58</div><div class="msg">why do we need simple onboarding? because we want to attract users who knows zero on Ethereum? Or because of somehting else?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 21:59</div><div class="msg">if because they are new to technology - don't we want to make them comfortable and safe (not only in UI) but also feature wise</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 21:59</div><div class="msg">so - currently public/group chats are not moderated -&gt; how many naive users will send funds before learning?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 22:00</div><div class="msg">if this is our target audience - should we think on any feature from this pov? e.g some ?pre-filtering? so just strangers can't talk to you by adding your public key. or ?safe-mode? where you can ?hide?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2017-12-14 22:07</div><div class="msg">We have our UXR starting soon!</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2017-12-14 22:08</div><div class="msg">These are all very good questions btw :slightly_smiling_face:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 22:10</div><div class="msg">Dapps thing - I think it's one of the most important benefits of Status: being a browser in mobile for Ethereum. So, the more Dapps are working in Status the better, so more collaborations/cooperation we have with Dapp developers the better. We can be slow with chats but we will be forgiven if 900 DApps can be opened and used via Status. Don?t we want to put emphasis there? Do we want to create stronger links with dev communities and encourage mobile versions etc and then enchance chats?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 22:10</div><div class="msg">It?s all about choices - we can easier get big audience by just being a gateway and then keep this audience in messenger and wallet</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2017-12-14 22:11</div><div class="msg">Having DApps accessible through "Home" would also provide the same functionality right?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2017-12-14 22:11</div><div class="msg">Also, are there 900 DApps in the market right now?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 22:11</div><div class="msg">there are &gt; 900 in State of the Dapps</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2017-12-14 22:12</div><div class="msg">I don't think anyone is saying remove DApps entirely, it's more a case of removing it from the bar - and then bringing it back when we have effective curation and structure to how users should interact with them</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 22:12</div><div class="msg">ok 877 (hey from the future:) ) <a href="https://www.stateofthedapps.com/">https://www.stateofthedapps.com/</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2017-12-14 22:12</div><div class="msg">I guess my point is that DApps are still accessible, and will remain in Home</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2017-12-14 22:13</div><div class="msg">Building out a proper Discover will require work which imo isn't a priority compared to Chat/Wallet/Performance/Onboarding. It may be easier for us to have this discussion on VC as well.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2017-12-14 22:13</div><div class="msg">Maybe @chad you can setup a #26 kick off call sometime next week so we can discuss the Now vs MVP doc?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 22:13</div><div class="msg">there is already huge list - ok we can filer out gambling probably or make user to add any Dapp as favourite to ?workaround? pre-filtering, does not matter. Now we have less than 10 on Ropsten and no possibility to save/bookmark your own url - this is a shame if one of our core features to be a Dapp browser</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 22:16</div><div class="msg">tbh, we were changing UI since spring and from how it went - we can do it for +6 month again (sorry if I?m to bold with assumptions as I?m not a developer) but re-designing UI once more can easily eat 3-4 months of the team effort with 1-2 month of stabilization. So, having goals and testing goals before implementing like with MVP mockup on real users can save us from re-designing UI or making choices what to implement now and what can be in version 2.0</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-14 22:45</div><div class="msg">Agree with Anna</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-14 22:46</div><div class="msg">Too late of a dependency imo</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-14 22:48</div><div class="msg">The reason onboarding isn't intuitive is because we got this feedback during fireside session, and it's also part of move away from having to be ?programmer? to use app to being more generally technically sophisticated, as far as I understand it</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-14 22:48</div><div class="msg">If this isn't the case and our personas we target are still devs then it doesn?t make sense to change it</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2017-12-14 22:54</div><div class="msg">so, define what we want to be in March by goals and reasoning behind them. Define audience/personas. Test current invison prototype on the representative group of users to validate the assumption that new ui is better. btw, would be great to test old UI on them too. Get the data and start solving most non-intuitive pieces but only if they are in scope. Having goals + audience would give us the scope. After this we can define how it can be achieved by set of features</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-14 23:01</div><div class="msg">@chad @andmironov having a fireside chat on prototype in Riot would be a good idea. Can have it next week. Also ask question de things we want to disable to make sure community is on same page. </div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-14 23:03</div><div class="msg">I think March is way to far ahead to be meaningful for scoping. Should be more iterative, short term and high resolution imo. Still thinking about how we can do this better across swarms</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-15 09:40</div><div class="msg">I think this comment by Jarrad a month ago is still relevant in terms of Beta scope: <a href="https://github.com/status-im/ideas/issues/19#issuecomment-344459745">https://github.com/status-im/ideas/issues/19#issuecomment-344459745</a></div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/fcc4675bd0ade27de9baefb82098e500.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0002-72.png" /><div class="message"><div class="username">yenda</div><div class="time">2017-12-15 10:33</div><div class="msg">Does the signup section in the document include new onboarding ? I suppose this should be part of the mvp as the current one is not satisfying</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-15 11:59</div><div class="msg">Yep. Check out invision for some mockups. Still need to build out idea brief.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2017-12-15 12:00</div><div class="msg">I?m confused, MVP=public beta release? or MVP is a codename for our internal build that we gonna make by March?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-15 12:03</div><div class="msg">the naming is unfortunate</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-15 12:07</div><div class="msg">MVP is the minimal state of the app we are aiming for (and are currently defining and scoping). If all goes to plan (technically, good user feedback, good performance, etc) we can release this as the beta.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-15 12:11</div><div class="msg">the thing is we call swarm's first iteration MVP (iteration 0 / a spike), and we also had the app up in Testflight as an alpha with users for 6m-1y, so what was that if not an MVP? that was a year ago.
As far as I understand it, MVP in sense @chad is using it is more clear in terms of being product-focused to test a product hypothesis, as opposed to laundry list of features. But for people who've been working here longer, it seems as if we already have something like this, and we have releases like 0.9.11, 0.9.12 which are alpha releases, and at some point we want to make this beta, where beta scope is roughly what is outlined in #26 with more high-resolution on the product offering.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-15 12:14</div><div class="msg">or am I missing something?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-15 12:14</div><div class="msg">Ah good distinction Oskar. Yes indeed I've been using it in the "lean startup" sense popularized by Eric Reis.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-15 12:14</div><div class="msg">yeah which makes complete sense and is the right way to do it, we just need to disentangle names so everyone knows what moon we are pointing to when we use our fingers</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-15 12:16</div><div class="msg">To the moon!!! :sweat_smile:</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/b11645e09683360c0849df16c77e9980.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">themue</div><div class="time">2017-12-15 14:43</div><div class="msg">@chad Thinking about chat and the simplified UI. The home view could get very long. Sorting it by last message or adding makes it difficult to get to one with a longer break, sorting it by alphabet makes it difficult to get to actual messages. And having dApps there too makes it even worse.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-15 14:49</div><div class="msg">I'm not too concerned during the beta. Works fine with imessage/wechat/mail and a bunch of others. And it can be easily fixed by adding search when we know it is a real user problem.</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/b11645e09683360c0849df16c77e9980.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">themue</div><div class="time">2017-12-15 14:54</div><div class="msg">OK, keep it in mind for user stories.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-15 15:17</div><div class="msg">I've heard some mention of bots. How do bots fit into Status?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-15 17:11</div><div class="msg">I got a request from `Yuan Lu` to view the MVP now vs MVP doc. Does anyone know who that is?</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/b11645e09683360c0849df16c77e9980.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">themue</div><div class="time">2017-12-15 17:20</div><div class="msg">@chad Branch <a href="https://github.com/status-im/ideas/tree/postgress%2F39-redefine-mvp">https://github.com/status-im/ideas/tree/postgress%2F39-redefine-mvp</a> grows. If you keep an eye on it I would be interested in your feedback.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-15 17:35</div><div class="msg">Oh cool thanks</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2017-12-15 19:28</div><div class="msg">No clue. </div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-15 19:31</div><div class="msg">Weird this doc must have been shared publicly?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2017-12-15 20:15</div><div class="msg">Mmmm not sure</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2017-12-16 07:08</div><div class="msg">Just to put my 2 cents in here on DApps viability for Beta / MVP ? DApps overall have a very small rate that we can actually use to-date, and even smaller that are mobile friendly in terms of UX (web interface leaves a lot to be wanted for most DApps) ? the State of the DApps (live) DApps list puts us under 300 see <a href="https://www.stateofthedapps.com">https://www.stateofthedapps.com</a> (filter by `Live`) ? and that list is very deceiving as many are Ponzi / halfway dead DApps or some that aren?t really even `live` yet. Ofc 2018 will be a big year for some of these bigger projects, the current state is very limited for ?functional, useful, friendly, mobile responsive? DApps for us to list natively. There could be some more that would be viable and i?d be interested to find those; but there is not an overwhelming list of ?fully functional and mobile friendly? DApps to date.
As far as user experience I think Leeroy would be an awesome one especially since we have @james884 that could help curate it to a good first open experience need, then of course CK, and EthLance has a friendly user experience for mobile. I think it's very key to pay attention to what the ecosystem is doing / wants now; before many of these awesome DApps actually become feasible.
<a href="https://youtu.be/P6Bosg9QKnw?list=PLaM7G4Llrb7y0sNzmHSyqd9Hni1cya8IH&amp;t=141">https://youtu.be/P6Bosg9QKnw?list=PLaM7G4Llrb7y0sNzmHSyqd9Hni1cya8IH&amp;t=141</a>
Infura Data on most popular DApps to date ^^ (cryptokitties will have changed that by now :slightly_smiling_face: )
And that is `exchange` ? the biggest ferver in Ethereum for the short term IMO until scaling becomes more of a reality with DApps will be decentralized exchanges like etherdelta / oasisdex and all of the relayers built on 0x etc. It would be amiss for us to not focus on the exchange functionality in the near term IMO as it's also a key piece of on-boarding users into SNT (eth&gt;snt) and also the short term focus of ethereum. Especially since there?s not a mobile app out there with the functionality of Status that would allow mobile DEX token / token exchange. Maybe something like swap <a href="https://www.youtube.com/watch?v=6p2_v80AdoY">https://www.youtube.com/watch?v=6p2_v80AdoY</a> (early release Q1 next year on main-net) or a non-native 0x relayer (already some live, have contact with a few the 0cean, ethfinex, radar relay and 0x itself) would be viable since we're not planning on native implementation for MVP, but it's something that will drive user-base for sure.
Outside of that I had a discussion with Chad about chatbots and how including some of the chatbots from our hackathon or even some that a few team members / community members made /make would be very useful from a first open perspective. Will be glad to be part of the Dogfooding as we test through viable first open experiences with DApps, chatbots and more thinking about Beta mvp as it's been something i?ve been thinking about myself a lot.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-18 11:31</div><div class="msg">Thanks for that insight @hutch! Good things to think about.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-18 11:32</div><div class="msg">After we get the core app trimmed down we can ensure a great first run experience.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-18 11:47</div><div class="msg">@chad As I think about it more, perhaps it does make sense to disable public chat from Beta / product MVP. A lot of uncertainty in that department. We can still work on getting it supported, but let's not make it a blocker and let's assume it won't be in. If it is, we'll get pleasantly surprised :slightly_smiling_face: I believe this is what you originally had in mind.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-18 11:50</div><div class="msg">Sounds good. I?m really think about Status as an onion with many many layers. Lets get the base then start adding layers as we go. </div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-18 11:51</div><div class="msg">(Especially when there is so much core work left)</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-18 11:52</div><div class="msg">Yeah, and Riot can make-do for now. We can still use dogfood as driver internally with a flag / desktop, just not main product focus / blocker</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-18 11:53</div><div class="msg">Thinking about MVP features what does everyone think of <a href="https://itunes.apple.com/us/app/cipher-browser-for-ethereum/id1294572970?mt=8">https://itunes.apple.com/us/app/cipher-browser-for-ethereum/id1294572970?mt=8</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-18 11:53</div><div class="msg">Looks a lot like wallet + dapp MVP</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-18 11:59</div><div class="msg">Nice to see some new players around :wink: No chat so not real competition. Now it depends what their vision is but they look focused on browsing DApps.</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-18 12:00</div><div class="msg">As of now they don't offer more than we do and are probably centralized (i.e. using infura?)</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-18 12:01</div><div class="msg">They get some good press. Sounds more frustration towards status as we are still rough around the edges</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2017-12-18 12:32</div><div class="msg">Nice idea to show network in the top left corner</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2017-12-18 12:32</div><div class="msg">and network switch works fine without rebooting the app</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-18 15:38</div><div class="msg">I took some screenshots and notes of the Cipher first-run experience.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-18 15:39</div><div class="msg">tl;dr This has been the first time on mobile that I've been able to easily discover and try out a few dapps. It is a super easy gateway into the world of ethereum, but it has some shortcomings.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-18 15:40</div><div class="msg">(more of these live in the team drive here <a href="https://drive.google.com/drive/u/0/folders/1jHKmwhThE54tFVo-zf48L1VQnjgonq44?ths=true">https://drive.google.com/drive/u/0/folders/1jHKmwhThE54tFVo-zf48L1VQnjgonq44?ths=true</a>)</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-18 15:42</div><div class="msg">Awesome! Which one felt smoother between Cipher and Toshi?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-18 15:44</div><div class="msg">hmmmmm Toshi is pretty slick in general, but it isn't a 1-1 comparison. In terms of Dapps, I preferred Cipher because it had a handful for me to discover. Toshi really just has 1 (cryptokitties).</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-18 15:44</div><div class="msg">But overall Toshi was much more polished.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-18 15:45</div><div class="msg">I liked that Cipher worked on iPhone X and used touch id and face id to make authenticating very smooth.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-18 15:46</div><div class="msg">So if you are on mobile and want dapps, hands down Cipher is better.</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2017-12-18 15:47</div><div class="msg">:+1:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2017-12-18 16:20</div><div class="msg">@chad great presentation on cipher ? it's also worth mentioning you can use their DApp browser in landscape mode (at one point you could do this with status too? opened up an issue in regards to it)
Many DApps will need this to work successfully. It?s even good to plan a future where DApps like Decentraland would work in status (eg, you need a full screen browser window for this?)</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-18 16:23</div><div class="msg">:thinking_face: Hmm why do you need landscape for DApps to work? I could see that Dapp creators don't optimize for mobile since there aren?t mobile browsers, but that will all change with Status.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2017-12-18 16:24</div><div class="msg">For example like FunFair ? the only way you can use their games is in landscape mode.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2017-12-18 16:27</div><div class="msg">(you can check it out on testnet on cipher)</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2017-12-18 16:28</div><div class="msg">There presumably will be more DApps that work better in landscape mode ? thinking along the lines of scroll based games etc.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2017-12-18 16:41</div><div class="msg">@chad</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-18 16:42</div><div class="msg">k good to know</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-20 13:31</div><div class="msg">Some notes from the prototype walkthrough <a href="https://docs.google.com/document/d/1Bkumb45cv7ShgSLE4FvB53SakTS_Y7G6SZCCzMkwq7M/edit#">https://docs.google.com/document/d/1Bkumb45cv7ShgSLE4FvB53SakTS_Y7G6SZCCzMkwq7M/edit#</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2017-12-20 13:39</div><div class="msg">@chad my 5 c: `Idea: If not on mainnet show red/yellow banner saying ?You are on Ropsten?` - we already have this but its not yellow or red)</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-20 13:50</div><div class="msg">Got a screenshot?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2017-12-20 13:52</div><div class="msg"><a href="http://prntscr.com/hq2a5z">http://prntscr.com/hq2a5z</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2017-12-20 13:52</div><div class="msg">its saying unknown now due to known bug - not fixed yet</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2017-12-20 13:53</div><div class="msg">if I understood the note correctly ofcourse. If not - please disregard :slightly_smiling_face:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-20 13:54</div><div class="msg">Sort of like that, but persistent throughout the whole app.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-20 13:55</div><div class="msg">I'm not sure what Oskar or Andrei had in mind, but when they said it I immediately thought of something like this</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-20 13:55</div><div class="msg"><a href="https://i.stack.imgur.com/BhRBU.jpg">https://i.stack.imgur.com/BhRBU.jpg</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-20 17:09</div><div class="msg">Hey <!here>! This last week has been really productive in working toward a vision for the beta. Thank you for your feedback on the prototype and docs! It appears we are really close with the app having many of the features we need. From now until launch will primarily focus on consolidating, refining, tweaking, and optimizing.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-20 17:11</div><div class="msg">do you think we should update the actual idea in <a href="https://github.com/status-im/ideas/issues/26">https://github.com/status-im/ideas/issues/26</a> and actualize it with people involved? and your vision etc, so it doesn't get lost</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-20 17:11</div><div class="msg">Instead of writing a granular doc of what feature will be in the beta, I've created a high level vision and goals doc that focuses on the core goal and mission of the app. Each swarm can then use these heuristics to make the right decisions (which I see is already happening :) Give the doc a read and let me know if you have any questions <a href="https://docs.google.com/document/d/1KY9E1hIhpVc3A-fYvLyGpncRa6zOFnAxMHDbG9pXh8o/edit#">https://docs.google.com/document/d/1KY9E1hIhpVc3A-fYvLyGpncRa6zOFnAxMHDbG9pXh8o/edit#</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-20 17:12</div><div class="msg">From here, each swarm will work to fulfil the high level goals and spec out the user stories and requirements in detail.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-20 17:13</div><div class="msg">Yep. As a comment (so we preserve history), or editing the main issue?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-20 17:14</div><div class="msg">I guess as a comment</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-20 17:14</div><div class="msg">editing main issue</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-20 17:14</div><div class="msg">I'd say you are main driver, take over from Jarrad and put me as contributor, or something like this</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-20 17:15</div><div class="msg">since shift is a bit towards product MVP as opposed to specific technical things, even if that is part of it</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-20 17:15</div><div class="msg">we can also leave it alone, create new idea that replaces it, and rename channel</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-20 17:16</div><div class="msg">yeah the shift makes sense since this is a "meta" issue. But I don't want to wipe out what is there. It impacts the comments too which were about the original work.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-20 17:16</div><div class="msg">what about new idea that replaces old? I think that's fine, even if it seems a bit funny</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-20 17:16</div><div class="msg">26 replaced 19 (my old one)</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-20 17:17</div><div class="msg">out with the old, and in with the new!</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-20 17:17</div><div class="msg">@naghdy any thoughts?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2017-12-20 17:34</div><div class="msg">I think re-using #26 is fine, and then write a comment pasting in the main concepts that have been removed</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-22 16:55</div><div class="msg">@chad FYI: In terms of performance being an issue for multiple person chat, it's only a problem for group chat. Public chat is completely fine and this has to do with how we currently do expensive encryption/decryption events.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-08-27/423671855091_1b4f90cfbdd6a3ee2b6f_72.jpg" /><div class="message"><div class="username">roman</div><div class="time">2017-12-26 12:22</div><div class="msg">i?m trying group chat locally on four device and don't see any specific issues there. When users send first message in the group chat (during the session) it'sslow, this is noticeable but after that i don't see any difference comparing to public groups and 1-1. Same lagging animation</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-26 13:23</div><div class="msg">Hm, Anna might have more details, but this has been recurring feedback re group chats in dogfooding sessions AFAIK. None of that jankiness existed in public chat</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-27 13:41</div><div class="msg">@jarradhope</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-27 14:21</div><div class="msg">Quick update: I walked Jarrad through the invision prototype and feedback was positive. :+1:
Some important feedback was emphasizing the importance of #24-onboarding to make sure we give new users a meaningful experience so we don't lose them.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2017-12-27 21:12</div><div class="msg">Updated #26 on github.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2017-12-27 21:14</div><div class="msg">thanks Chad!</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-02 13:23</div><div class="msg">@chad Re user feedback guiding us (great point to re-iterate), Github issues might not be optimal for all users. In addition, we can use something like <a href="https://canny.io">https://canny.io</a> Example: <a href="https://react-native.canny.io/feature-requests?sort=top">https://react-native.canny.io/feature-requests?sort=top</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-02 13:32</div><div class="msg">Looks cool. @hester will have some insight here (new UXR)</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-02 15:21</div><div class="msg">Quick beta update: Today #61-app-structure had a kick off and work is starting on simplifying the app for the beta launch! Check the channel for more info.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-02 17:18</div><div class="msg">Not sure if anyone else noticed but in Invision @andmironov added unread badge notifications which helps users see if there are new messages whilst using Status in different contexts. This is a great idea! I've personally been using Status and thought it was broken because I assumed I wasn't getting new messages, when actually the messages were there but I wasn't notified. <a href="https://github.com/status-im/status-react/issues/2871">https://github.com/status-im/status-react/issues/2871</a>
Not sure what Swarm this fits into but I'd argue it would make an important beta addition.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-02 17:28</div><div class="msg">@oskarth We also discussed today about fixing the logout issue, which kinda fits into misc UX beta improvements. I imagine the more we dogfood the app, and the closer we get to beta we are going to have a bunch of misc UX issues that should be fixed. Does it make sense to have a beta UX polish swarm that addresses these miscellaneous issues we encounter? Or fit them into current swarms?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-02 17:30</div><div class="msg">Can we punt on this decision a bit? Until we really got going with big swarms and know more about availability </div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-02 17:31</div><div class="msg">sure thing. shall we give issues like this a beta tag so we can keep track?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-02 17:31</div><div class="msg">In meantime we can bounty it and see if it gets solved, should also consider prio if it is blocking release or not imo. Then we can revisit it in, say, 2w</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-02 17:31</div><div class="msg">I personally wouldn't bother because there are 100 of such issues imo, but if you want to go ahead </div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-02 17:31</div><div class="msg">:+1:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-02 17:32</div><div class="msg">I?m going to add a bounty of it this week too so hopefully we get naive solution anyway </div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-02 17:32</div><div class="msg">For those 100 we should be prioritizing.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-02 17:32</div><div class="msg">Feel free to suggest bounties too btw :) #10-ob-bounties </div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-02 17:32</div><div class="msg">Yep agree</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-02 17:33</div><div class="msg">Not sure the best way to do it. GH milestones can be ordered. There are projects, but these don't really fit it. Perhaps a ?beta misc shit? milestone that is kept ordered :stuck_out_tongue:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-02 17:33</div><div class="msg">In general I think swarms with coherent focus/vision better than ?misc fixes? type or swarms, not very inspiring/never ending, unless part of coherent vision for that swarm </div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-02 17:34</div><div class="msg">IME/IMO prioritization doesn?t make sense/mean much outside of prio 1 and 2, cause things change a lot</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-02 17:34</div><div class="msg">Agreed, but we still have 100 issues that need to be addressed/triaged/prioritized and at least from my POV i don't have any visibility over that</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-02 17:35</div><div class="msg">Anyway, something to chew on.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-02 17:35</div><div class="msg">But you can have a Chad wish list that you order however you want and people can pick stuff off it if they are out of important things to work on :p</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-02 17:36</div><div class="msg">Right, this is true. I think this is part of general issue triage, and is likely a never ending process</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-02 17:36</div><div class="msg">I like your idea of having this be based on quantitative user feedback, automatic prioritization based on reality </div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-02 17:37</div><div class="msg">And something we can all see/discus/contribute.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 16:41</div><div class="msg">Thread about rough tracking -&gt; @adamb @chad</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 16:42</div><div class="msg">&gt; Track total messages volume?
&gt; Hack: Wnode dir file size
&gt; Won?t be super accurate but it can be set up. We have a bunch of Whisper nodes that also could be monitored. The best would be to actually collect numbers from Whisper service itself
&gt; what is something we can do in a few hours? even super rough</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-01-05 16:43</div><div class="msg">Ok, what do we want to achieve? :smile:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 16:43</div><div class="msg">^ @chad</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-01-05 16:43</div><div class="msg">If we get `100 MB per hour of messages` how will it be useful?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 16:43</div><div class="msg">not absolute numbers, interesting if we get 100 first week, 120 second, etc, % key</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 16:44</div><div class="msg">it's a form of KPI right</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 16:44</div><div class="msg">Testflight installs -&gt; Active users -&gt; (later) transacting users</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-05 16:45</div><div class="msg">Yes it would really help us gauge status usage and measure how we are doing. We want that number to be going up! A simple daily volume chart would be great.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-05 16:47</div><div class="msg">Currently we don't have many feedback loops to understand the impact of our work. Jarrad said that SNT price is one, but I'd love to introduce some user/product focused ones.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-01-05 16:47</div><div class="msg">Ah I see. This can be definitely answered by collecting some metrics from our cluster nodes.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-01-05 16:48</div><div class="msg">We can test it with MailServer as it's the only status-go node running I guess</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-05 16:48</div><div class="msg">can't wait until we can post one of these <a href="https://telegram.org/blog/15-billion">https://telegram.org/blog/15-billion</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 16:48</div><div class="msg">I think monthly contributors (org goal 1) we have and is outside of code base and can fairly easily be measured, even without engineers, also transacting users SNT (org goal 2) we can do proxy outside of core product (query blockchain, gets traders too but still counts a bit). But I defo agree, it'd be nice to have some in core app too</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-01-05 16:50</div><div class="msg">Yeah, but if we?d like to actually see if people talk to each other through Whisper we need to track whisper envelopes</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 16:50</div><div class="msg">agree</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-05 16:50</div><div class="msg">Eventually would love to see Status DAU,/MAU, daily/monthly message volume, daily/monthly SNT volume</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-05 16:51</div><div class="msg">DAU/MAU needs to be done with app tracking code, but the others can be done externally which is a good place to start</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 16:52</div><div class="msg">yep</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-05 16:52</div><div class="msg">&gt; we can do proxy outside of core product (query blockchain, gets traders too but still counts a bit)
We can get that now and is significant ($177M in last 24 hour), but $0 in-app :disappointed:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-05 16:52</div><div class="msg">pretty big delta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-05 16:53</div><div class="msg">Will there be a technical way to query the blockchain by client or other way to identify transactions originating from Status?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 16:53</div><div class="msg">haha true</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 16:53</div><div class="msg">some for SOB though!</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 16:53</div><div class="msg">:stuck_out_tongue:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 16:53</div><div class="msg">uhmm not sure, good question</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-05 16:54</div><div class="msg">@cryptowanderer is killing it!</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 16:54</div><div class="msg">^ @jarradhope @3esmit ?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 16:54</div><div class="msg">I think it'll be difficult but don't know too much in detail of what we can get from transactions</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 16:55</div><div class="msg">it might also be a privacy thing, but one could imagine an anonymous "tag" for in-app tx, like you can tag bitcoin tx I know</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-05 16:55</div><div class="msg">Markets are tracked, eg <a href="https://coinmarketcap.com/currencies/status/#markets">https://coinmarketcap.com/currencies/status/#markets</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 16:55</div><div class="msg">@chad you have lots of good thoughts and questions around this, would be great if we oculd gather this in a doc somewhere so it doesn't get lost</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 16:56</div><div class="msg">yeah not sure where this data is from exactly tbh</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-05 16:58</div><div class="msg">It is going to be a great morale booster for the team to see those message and transactions numbers going up. Winning feels good :slightly_smiling_face:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-01-05 17:20</div><div class="msg">let?s capture this effort for MailServer in an issue</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-01-05 17:21</div><div class="msg">is there anything relevant already or should I create it?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-01-05 17:21</div><div class="msg">I can implement it next week as we have some pieces already done that help with that</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 17:23</div><div class="msg">If you could create it that?d be great </div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 17:23</div><div class="msg">Awesome :)</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-01-05 17:23</div><div class="msg">ok</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-05 17:33</div><div class="msg">@adamb Just curious: do you have thoughts on how to store and view this captured data?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-01-05 17:35</div><div class="msg">@chad Grafana to display data + some storage. I have seen good stuff with InfluxDB and Telegraf.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-05 17:36</div><div class="msg">Sounds good. Was gonna suggest InfluxDB :nail_care:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-01-05 17:39</div><div class="msg">Feel free to add more details/requests: <a href="https://github.com/status-im/status-go/issues/536">https://github.com/status-im/status-go/issues/536</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-05 17:41</div><div class="msg">Ok cool. Do you mind if I write a broad ?metrics? idea issue draft? This can encompass message tracking, SNT tracking, and in-app tracking.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-01-05 17:42</div><div class="msg">@chad sure, that sounds great!</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-01-05 17:43</div><div class="msg">I think we can use MailServer as PoC and in the future we should a bit redesign our cluster and then we can collect metrics from more nodes which should be more accurate</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-05 17:44</div><div class="msg">Sounds perfect. We can scale up our needs as volume scales :slightly_smiling_face:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-01-05 18:16</div><div class="msg">just a random question @oskarth @adamb: one of the things we want to do for the #ArtProject (which is about midway through this year) is track messages going through our `masternodes` (wnodes, whatever) and then map these onto a physical structure - do you think we could leverage off this kind of thing?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 18:17</div><div class="msg">Possibly! WDYT @adamb?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-01-05 18:17</div><div class="msg">@cryptowanderer yeah, @divan and I would like to provide metrics that will allow to visualize exactly that :slightly_smiling_face: However, I am not sure what you mean by `physical structure` :stuck_out_tongue:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-05 18:18</div><div class="msg">I think it?d be really cool to tie this in at multiple points: product kpi, network sanity/overview, zero knowledge tracking, art project - lots of overlap </div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-01-05 18:18</div><div class="msg">@adamb <a href="https://github.com/status-im/ideas/issues/66">https://github.com/status-im/ideas/issues/66</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-01-05 18:20</div><div class="msg">@oskarth yeah, all these metrics won't have assumptions, they will be as plain and generalized as possible so almost anything will be possible to build on top of them</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-08-27/423671855091_1b4f90cfbdd6a3ee2b6f_72.jpg" /><div class="message"><div class="username">roman</div><div class="time">2018-01-06 08:42</div><div class="msg"><a href="https://status-im.slack.com/archives/C8B97QM5K/p1515227984000004">https://status-im.slack.com/archives/C8B97QM5K/p1515227984000004</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-08 09:39</div><div class="msg">@chad @cryptowanderer @hutch let's close this tomorrow unless we have a decision to include it or not, we can always reach out to them again if situation change <a href="https://github.com/status-im/status-react/pull/2776">https://github.com/status-im/status-react/pull/2776</a> (want to have minimal amount of PRs open)</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-08 15:00</div><div class="msg">@hester</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-12/285244060371_dbc007c8c7963b36a3ee_72.jpg" /><div class="message"><div class="username">hester</div><div class="time">2018-01-08 15:00</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-10 14:39</div><div class="msg">@andmironov @denis-sharypin and others, what do you think about having Invision push design updates to Slack? It is a very low effort way to keep everyone in the loop on design changes. We can either post it here for the beta updates, or maybe in the design channel to keep things design related.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-01-10 14:42</div><div class="msg">Will it be as Activity tab in invision?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-01-10 14:42</div><div class="msg">how do you see that ? Like an export of everything new by EOD? i will be quite noisy to see each font update )</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-10 14:44</div><div class="msg">Yeah similar to activity tab, but will give everyone access.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-10 14:44</div><div class="msg">Nastya <a href="https://support.invisionapp.com/hc/en-us/articles/205063069-How-do-I-share-content-and-activity-via-Slack-">https://support.invisionapp.com/hc/en-us/articles/205063069-How-do-I-share-content-and-activity-via-Slack-</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-01-10 14:45</div><div class="msg">cool</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-10 14:45</div><div class="msg">Right now there aren?t a lot of updates. If it gets too busy we can always move it to a dedicated channel like #design-updates (similar to #internal-jenkins or #test-team github)</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-01-10 14:46</div><div class="msg">sounds good anyway - great initiative</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-10 14:47</div><div class="msg">So lets do #design-updates so it doesn?t get in anyones way? (People can mute the channel if they want and pop in when they need to)</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-01-10 14:48</div><div class="msg">yep lets try that and see :slightly_smiling_face:</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-01-10 14:52</div><div class="msg">That would be awesome! I don't have an invision account so can't see those changes</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-10 14:55</div><div class="msg">You should get an account! You can see full history of screens, a single screen with new updates, comments view to easily see and respond to all comments, etc etc. Maybe ping @andmironov</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-10 15:00</div><div class="msg">This has been setup. New comments, screens, and updates will go to #design-updates</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-01-10 15:11</div><div class="msg">hey, this seems cool, thanks!</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-10 15:23</div><div class="msg"><!here> To help with beta and design visibility all Invision design updates and comments will now be posted in #design-updates. Take a :eyes:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-01-10 16:48</div><div class="msg">tracking bad.. however saying that, LES2 Observer Chains and Chain Filters might be interesting to us. <a href="https://github.com/zsfelfoldi/ethereum-docs/blob/master/les/filter_observer.md">https://github.com/zsfelfoldi/ethereum-docs/blob/master/les/filter_observer.md</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-10 17:15</div><div class="msg">@chad do we need location for MVP?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-10 17:15</div><div class="msg">I think maybe it adds some more annoying problems and maybe it makes sense to disable it, not sure</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-10 17:18</div><div class="msg">#61-app-structure decided to keep it if works fine, or remove it if there are issues. Currently there are 23 open issues relating to /location, so it may not make it into the beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-10 17:19</div><div class="msg">Swarm will make the determination next iteration when we focus on Home/Chats</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-10 17:20</div><div class="msg">ok, but principally we are fine with removing it?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-10 17:20</div><div class="msg">Yes</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-10 17:20</div><div class="msg">it's possible another swarm (like 64) decide to remove it, but will obv coordinate with 61</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-10 17:21</div><div class="msg">ok</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-10 17:21</div><div class="msg">@jeluard cc</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-10 17:21</div><div class="msg">or even 55 cause perf somtimes bad for it</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-10 17:22</div><div class="msg">I?m all in favour of (temporarily) omitting features if it slows us down without having a big enough pay off.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-10 20:24</div><div class="msg">Created a channel and issue for core metrics #68-core-metrics <a href="https://github.com/status-im/ideas/issues/68">https://github.com/status-im/ideas/issues/68</a></div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-01-11 14:37</div><div class="msg">Any opinion about using infura or local node for the MVP?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-11 14:49</div><div class="msg">Infura. fixing perf for local is big task, shouldn?t block. </div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-11 14:49</div><div class="msg">Should disable these by flag, meant to put up bounty but haven't yet </div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-01-15 14:24</div><div class="msg">Do we know that local node is a huge performance hit ?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-01-15 14:24</div><div class="msg">I haven't seen any numbers on it that have been isolated to LES</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-16 07:59</div><div class="msg">Qualitatively I believe so (hot phone during sync), but no hard numbers other than Ivan D's LES CPU checks (assuming status-go bottleneck and high CPU~&gt;high temperature).
IMO it makes sense to decouple this from perf work for beta/55-fast status work:
1) It makes the general problem (bad perf/UX) easier if we can ignore areas with large surface (such as LES work)
2) Investigating it further takes away from Go resources, which we are already lacking in 55 swarm. These efforts are better spent on testing Whisper CPU/network overhead hypotheses, as these are things we must-must have.
That said, we should definitely investigate at some point, especially when we have more bandwidth in this area. I would expect the group that is dedicated to LES work in general be very interested in this task.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-01-16 08:38</div><div class="msg">okay sounds good</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-16 15:40</div><div class="msg">tl;dr Beta team is exploring simplifying chats by consolidating p2p and group chats into just one chat. Read more...</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-16 15:40</div><div class="msg">Status currently has three types of chats: Private peer to peer chats (for 2 people), private group chats (for 2 or more people), and public group chats. Private peer to peer and group chats are practically identical, with the only difference being that additional people can be added to the chat. The team is proposing simplifying the UI and UX by combining p2p/group and to simply have two types of chats: Private and Public.
Here is a mockup of the proposed changes <a href="https://projects.invisionapp.com/share/KXEWN9XHM#/screens/268973247">https://projects.invisionapp.com/share/KXEWN9XHM#/screens/268973247</a>
This is a similar convention to many other chat apps out there, offers users flexibility, and is pretty much working already in the app. The changes will be minimal and mostly UI.
Work is currently in explore phase. Holla if you have any opinions on this!</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-16 15:43</div><div class="msg">If we end up shipping without group chats, what would the graceful degradation look like? Just not allow more than one check mark?
While it looks quite nice I'm worried about us taking on more and more work, while we should be doing less. Is this on the critical path of the MVP? Considering everything else we want/need to do (61, 55, 24 (not really started yet).</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-16 15:44</div><div class="msg">To me it seems more like a feature request that we can bounty up. Additionally, I believe the actual code works quite differently for 1on1 and group chats, so it's definitely not a non-trivial change.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-16 15:48</div><div class="msg">Group chats work just fine for 1 on 1 chats. I see it as more about focusing on that UX</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-16 15:49</div><div class="msg">No critical path just yet. Just in explore phase. </div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-16 15:50</div><div class="msg">I think we should explore this outside of beta in that case, more as general UX improvement</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-16 15:50</div><div class="msg">we are already spread quite thin (too thin possibly) so the challenge IMO is to focus in</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-16 15:50</div><div class="msg">maybe if people generally agree with UX we can bounty it up as experimental feature? that way it doesn't take away any core focus</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-16 15:56</div><div class="msg">Group and public chats are still candidates for the beta so we are having a holistic look at all chats. There is very little cost to design explorations so I?m happy to keep thinking about making the beta the best it can be for core UX. A little bit of exploration now can save a lot of time later. </div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-01-16 16:01</div><div class="msg">All for design explorations :slightly_smiling_face:</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/b11645e09683360c0849df16c77e9980.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">themue</div><div class="time">2018-01-16 16:08</div><div class="msg">One little hint about the importance for a good UX: <a href="https://twitter.com/CivilBeat/status/953127542050795520">https://twitter.com/CivilBeat/status/953127542050795520</a>
The combination of simple usage and avoidance of errors is pretty important for the success of Status from day 1.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-01-18 10:13</div><div class="msg">public and private chats is good distinction</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-01-24/304281668629_99d09ae86c8e0a04b52d_72.png" /><div class="message"><div class="username">growbot</div><div class="time">2018-01-19 14:21</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-01-26 16:01</div><div class="msg">Quick Friday update:
- Lots of new UX improvements happening in #61 including a new DApp browser UI, tab UI improvements, and a beautiful new Profile screen and QR viewer.
- Many many many bugs fixed in #64 and one step closer to better and regular releases.
- Progress toward mainnet with a security audit kicking off in #58.
- Continued performance improvements in #55.
- Regrouped onboarding team for #24 with a new kick off happening soon.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-13 06:06</div><div class="msg">Hey everyone! This idea/meta issue has been neglected a bit. Would people find it useful to gather swarm leads / other stakeholders and have a call every now and then and talk about progress/blockers/timeline?
@andmironov (24 lead), @jeluard (61 lead), @adamb (58 lead), @dmitryn (55a/76 lead), @jeka (55b/71 lead)
General: @anna, @chad, @jarradhope, @naghdy, @jonny.z
(Of course, if people think it'd just be another meeting we don't have to do it)
:thumbsup: if yes, :thumbsdown: if no</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-02-13 15:51</div><div class="msg">Do we have a target date for the beta? Alternatively features we must have for the release?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-02-13 15:52</div><div class="msg">Have been aiming for end of Q1.</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-02-13 15:53</div><div class="msg">Do we have a plan when it comes to feature freeze, to prevent last minute regression?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-13 15:59</div><div class="msg">This is what 64 release is about</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-13 15:59</div><div class="msg">So one release will have essential scope to be good enough for beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-02-13 17:36</div><div class="msg">So can we merge?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-14 06:45</div><div class="msg">merge?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-14 06:47</div><div class="msg">we should have it monday but I'm really off then, hum</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-14 06:48</div><div class="msg">I'll plan it for Monday and do my best to attend, also for next Monday. Right after leads call</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-14 06:48</div><div class="msg">possibly we can have it 30m earlier if we do shorter leads call?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-14 06:56</div><div class="msg">Set up call to just after leads, we can also potentially have it 30m earlier if leads is abbreviated. We should probably have it as soon as possible, so I set it up for Monday and then next Monday as well. Technically I'm on vacation this Monday, so I'm still 'maybe', but I'll do my best to join. If not then perhaps someone else can facilitate and make sure we touch all major points. There's a doc in invite where we can formulate agenda</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-02-14 13:25</div><div class="msg"><a href="https://status-im.slack.com/archives/C8HGM58AU/p1518526826000148">https://status-im.slack.com/archives/C8HGM58AU/p1518526826000148</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-02-14 13:26</div><div class="msg">The onboarding swarm is ramping up ^^^. Everyone please check out the mockups and leave comments in Invision if you have any, or join #80-onboarding to discuss</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-02-14 18:52</div><div class="msg">I created a project board for the beta. A tidy way to see everything in one place. <a href="https://github.com/orgs/status-im/projects/13">https://github.com/orgs/status-im/projects/13</a>?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-15 03:09</div><div class="msg">Updated invite so it is clustered with leads call. Also definitely back then</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-02-15 15:00</div><div class="msg">Is the security audit also here?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-02-15 15:01</div><div class="msg">Yes it is!</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-02-15 15:01</div><div class="msg">:slightly_smiling_face:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-02-15 15:01</div><div class="msg">Do you think it makes sense to add individual bugs into this as well?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-02-15 15:01</div><div class="msg">Just to give people a clear idea of *all* the launch blockers</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-02-15 15:02</div><div class="msg">Then we can share it in #core, and everyone has a clear idea of exactly what the most important things are to fix</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-02-15 15:02</div><div class="msg">Probably not. This is purposely high level.
Each swarm has their own board full of bugs and issues.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-02-15 15:02</div><div class="msg">Eg this is for #61-app-structure <a href="https://github.com/status-im/status-react/projects/9">https://github.com/status-im/status-react/projects/9</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-02-15 15:07</div><div class="msg">But to your point, I?m hoping we can have a prioritized list in #75-status-everyday of issues that might not fit into the other swarms. A sort of important catch all of bugs and issues that surface during testing and user feedback.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-21/319502977622_385c355d598cd6a89bb0_72.png" /><div class="message"><div class="username">ricardo565</div><div class="time">2018-02-16 16:09</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-02-16 18:34</div><div class="msg">I might not be able to make this meeting. I have a flight at 6am and will try to make it, but may get stuck in the airport.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-02-21 01:12</div><div class="msg">@chad set the channel topic: <a href="https://invis.io/KXEWN9XHM#/269041131_Onboarding1">https://invis.io/KXEWN9XHM#/269041131_Onboarding1</a>
Board: <a href="https://github.com/orgs/status-im/projects/13">https://github.com/orgs/status-im/projects/13</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 11:50</div><div class="msg">If not we can keep it going for a bit longer (since we might need more than 30m anyway)</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/9a90059210aaacfa5550a12d39020469.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0022-72.png" /><div class="message"><div class="username">jeka</div><div class="time">2018-02-21 11:52</div><div class="msg">Could we keep old time? I can not have time to come from lunch for the rest of the time.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 11:56</div><div class="msg">ok sorry you are right, it is too last minute</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 13:01</div><div class="msg"><a href="https://meet.google.com/ntf-oxan-saz">https://meet.google.com/ntf-oxan-saz</a> call starting</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 13:01</div><div class="msg"><a href="https://docs.google.com/document/d/1vS_-pUps5aFFFzcqDIW5v0-gPs0A5e_NGLhWILuLV4Q/edit#">https://docs.google.com/document/d/1vS_-pUps5aFFFzcqDIW5v0-gPs0A5e_NGLhWILuLV4Q/edit#</a> meeting notes</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-02-21 13:02</div><div class="msg">Don't have access</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 13:02</div><div class="msg">try now</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 13:03</div><div class="msg">@naghdy able to join?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 13:03</div><div class="msg">since I fucked up invite by moving it around I can't find initial RSVP</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-02-21 13:03</div><div class="msg">No I can't. I've got a conflict</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 13:03</div><div class="msg">ok</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-02-21 13:03</div><div class="msg">I thought you were moving it for me, but yeah</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-02-21 13:03</div><div class="msg">ill definitely read the notes after</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 13:03</div><div class="msg">oh</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 13:03</div><div class="msg">is there some way I can see conflicts in google calendar? I missed this</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 13:04</div><div class="msg">@dmitryn?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-08-27/423671855091_1b4f90cfbdd6a3ee2b6f_72.jpg" /><div class="message"><div class="username">roman</div><div class="time">2018-02-21 13:05</div><div class="msg">@dmitryn is on another call as well </div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 13:05</div><div class="msg">oh</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 13:05</div><div class="msg">conflict</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 13:05</div><div class="msg">would be great if I could learn how to use a calendar and see conflicts :fine:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-24/320320314756_fe0f3ce0bb820f1aa8e3_72.jpg" /><div class="message"><div class="username">dmitryn</div><div class="time">2018-02-21 13:08</div><div class="msg">sorry, i?m on another call with 76 swarm guys</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 13:08</div><div class="msg">np was my bad</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 13:45</div><div class="msg">Notes in doc, next meeting on Monday</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 13:46</div><div class="msg">Specific action for now I personally committed to that was seen as useful by all devs present: create more global overview for Status Core iteration, i.e. one board where we put high prio issues over some timeframe (2w) that then each swarm owns</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 13:47</div><div class="msg">Additionally something open and to work on: more clear acceptance criteria for each swarm to clarify must have vs nice to have (expressed need from QA and other fronts)</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 13:47</div><div class="msg">cc @naghdy @chad</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-02-21 15:50</div><div class="msg">When you create a meeting, add guests and go to ?Find A Time? tab. Unless that was not really a cry for help then ignore me :smile:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 15:51</div><div class="msg">thanks! i'll try next time</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 15:51</div><div class="msg">it was</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-21 15:51</div><div class="msg">:stuck_out_tongue:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-09-12/240066984213_b35ca6f6b9658bf5cabb_72.jpg" /><div class="message"><div class="username">jonny.z</div><div class="time">2018-02-21 20:53</div><div class="msg">@chad @oskarth @naghdy @adamb do you guys have a proposal response from Deja Vu on the security audit? We are briefing the copywriter on the blog post announce tomorrow and it would be good to provide him with as much technical detail on the audits as possible. Thanks guys cc @kim196</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-02-22 05:22</div><div class="msg">No update from them yet. Will respond as soon as we know more</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2018-02-22 09:55</div><div class="msg">so there are 2 projects <a href="https://github.com/orgs/status-im/projects/13">https://github.com/orgs/status-im/projects/13</a> (contains only swarms/ideas) and <a href="https://github.com/orgs/status-im/projects/12">https://github.com/orgs/status-im/projects/12</a> (contains issues and ideas). I assume we want to track critical bugs to be fixed for milestone 1 ?Bangkok? which goal is `Getting stable app` (or correct me if it's something else please) in <a href="https://github.com/orgs/status-im/projects/12">https://github.com/orgs/status-im/projects/12</a> From what it looks to me there are some bugs that are not really critical for such milestone like <a href="https://github.com/status-im/status-react/issues/2622">https://github.com/status-im/status-react/issues/2622</a> Can we somehow sync on the goal, who triages the bugs and how often? If we are going to track scope of the bugs/features in other way - what?s the way? @oskarth @chad @naghdy I also assume that we wil have a milestone 2 ?Beta? with goal like `Fast reliable messenger` or anything else, so some other project will be created/maintained. Is is true?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-22 09:55</div><div class="msg">Agree, I talked with Nabil about stuff we brought up on 26 call. Waiting to hear from Chad as well</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-22 09:57</div><div class="msg">also talked to Igor about his experience at Opera and looking at how other teams do it, I'm a bit hesitant about moving "from" autonomous swarms to this global view so would be nice if we do it right and don't re-create some kind of top-down structure. Still unclear exactly best way to do this, at least to me</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-22 09:58</div><div class="msg">immediate proposal is something like: have a weekly project board with issues, swarms label and put issues on it that they plan/promise to complete during that week, and generally these are/should be high prio ones</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-22 10:01</div><div class="msg">Key seems to be (a) fixed iterations (i.e. weekly) (b) descoping (i.e. only put things that will be realistically accomplished, and generally get better at breaking down deliverables</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-02-23 07:06</div><div class="msg">For the short term, the goal was to have a stable version of the app to be usable in BKK. Then the second project was for the Closed Beta mainnet milestone, which is less time urgent.
After discussing this process with people over the past few days, it seems as though the main area to improve is swarm management. This includes the processes (incl. onboarding) of the swarm, as well as the success metrics/exit criteria.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-26 12:46</div><div class="msg">@chad you joining call in 15m?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-26 12:47</div><div class="msg">Do people feel like we have anything in particular to talk about that isn't dealt with in individual swarms?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-26 12:47</div><div class="msg">If not we can just skip it</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-26 12:48</div><div class="msg">@andmironov @jeluard @naghdy @jeka </div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/9a90059210aaacfa5550a12d39020469.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0022-72.png" /><div class="message"><div class="username">jeka</div><div class="time">2018-02-26 12:50</div><div class="msg">I've only swarm related news and questions. I think we can skip today's call.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-02-26 12:52</div><div class="msg">I?m available for the call.</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-02-26 12:55</div><div class="msg">Nothing special from me</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-26 12:57</div><div class="msg">ok let's cancel</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-26 12:57</div><div class="msg">@chad we are talking in 1on1 anyway, we can move it forward 30m if you want?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-02-26 13:02</div><div class="msg">I'm on the call... not sure if its happening</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-02-26 13:02</div><div class="msg">ok looks like its cancelled</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-26 13:03</div><div class="msg">sorry should've notified in chan</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-02-26 13:03</div><div class="msg">Re org / boards etc, this is still latest
&gt; After discussing this process with people over the past few days, it seems as though the main area to improve is swarm management. This includes the processes (incl. onboarding) of the swarm, as well as the success metrics/exit criteria. -- Nabil 3d ago</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-02-28 13:03</div><div class="msg"><a href="https://status-im.slack.com/archives/C8HGM58AU/p1519820381000113">https://status-im.slack.com/archives/C8HGM58AU/p1519820381000113</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-02-28 13:04</div><div class="msg">Some great progress in #80-onboarding</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-21/289215424480_9e6b0b7d07d153d54b60_72.png" /><div class="message"><div class="username">botbridge</div><div class="time">2018-03-13 02:50</div><div class="msg">has joined #26-beta</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-03-16 00:05</div><div class="msg">I've been thinking about the closed beta mainnet release and how it will likely drive so much new interest in Status! :tada:
But this will be an issue because we are maxed out at 10k iTC users and the clean script isn't removing enough to make room. (there is an addon to make this better but it isn't compatible with our build number format :disappointed: )
Out of the 10k Testflight accounts only 2.1k have installed 0.9.14. So I propose that for the beta we clean slate and delete all 10k testflight users. We then email all of them letting them know that to get the beta they have to go to the boarding form and signup.
Thoughts? @jonny.z @hutch @cryptowanderer</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2018-03-16 00:06</div><div class="msg">Sounds like a purgers dream</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-09-12/240066984213_b35ca6f6b9658bf5cabb_72.jpg" /><div class="message"><div class="username">jonny.z</div><div class="time">2018-03-16 05:43</div><div class="msg">I agree with this. @kim196 let?s define some launch comms so this is crystal clear to people. </div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-03-16 05:45</div><div class="msg">For Android the limit is set to 30k. Should we up that to max or do you want some scarcity?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-03-16 06:07</div><div class="msg">That sounds ok, though people might be bleak about having to re sign up... Still, seems like best solution for now</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-09-12/240066984213_b35ca6f6b9658bf5cabb_72.jpg" /><div class="message"><div class="username">jonny.z</div><div class="time">2018-03-16 06:40</div><div class="msg">It?s not ideal, true. But I think we can put a positive spin on it. And encourage people for beta. Is it easy enough to up the max? I think we should for sure </div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-09-12/240066984213_b35ca6f6b9658bf5cabb_72.jpg" /><div class="message"><div class="username">jonny.z</div><div class="time">2018-03-16 06:41</div><div class="msg">We going to pilot some paid advertising which hopefully drives installs and use </div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-03-16 06:51</div><div class="msg">AFAIK there isn't a play store limit. We can just up the number.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-03-21 10:59</div><div class="msg">@chad in terms of `Successfully launch Status` OKR i don't see clear scope of functionality that is expected for Beta launch. I would like to have this defined , seems very important to me. any plans on that? Am i missing something?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-03-21 11:05</div><div class="msg">The OKR shouldn?t have beta scope. That is up to the swarms that decide how to `Successfully launch Status`. (although we do have some hard blockers like mainnet, security audit, reliable messages, etc)</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-03-21 11:06</div><div class="msg">so is anyone deciding that? :slightly_smiling_face:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-03-21 11:24</div><div class="msg">Sorry what do you mean?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-03-21 11:25</div><div class="msg">i mean we have clear understanding that we need mainnet + messaging + audit for Beta. But it seems that is it . Personally I am expecting we deliver some cool features in Beta along with exisiting ones that will be improved. So I want to have the list of features that we want / should have for beta.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-03-21 11:28</div><div class="msg">Right! So someone might see the `5k DAU` goal and think we need to have Feature X to get it. They would then write a Idea (making sure we have solid success and exit criteria) and get feedback from the team. If there is a support a swarm will start and ship it! :slightly_smiling_face:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-03-21 11:29</div><div class="msg">but i think we should be all aligned on Beta expectations so nothing imprtant is missed by June 1</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-03-21 11:30</div><div class="msg">I think I see where you are coming from. The OKR doc is about aligning results, but you want to be aligned on features?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-03-21 11:31</div><div class="msg">yes!</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-03-21 11:33</div><div class="msg">To help with that we will have town halls every 2 weeks, and each swarm lead will update on the swarm they are working on. This should help a lot to get everyone on the same page to see the full extend of core work.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-03-21 11:38</div><div class="msg">but what is we want some feature for beta that does not have swarm yet?)))</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-03-21 11:41</div><div class="msg">Start the idea :slightly_smiling_face:
If it is super amazing everyone will want to do it.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-03-21 11:52</div><div class="msg">well i am worrying as because time is limited and we may be focusing on something that is not important for beta instead. That is my concern. So I am suggesting to list the features we want to have for beta in order to deliver super cool and attractive application, so we might want to think about something specific we want to include, something cool for example any game dapp/ useful dap / stickers etc that people really like so we will have an audience growth as a result of beta launch</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-03-22 11:00</div><div class="msg">I think this is a great point you bring up @nastya</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-03-22 11:00</div><div class="msg">How do you think this fits into the swarm model? Most work is done in individual swarms, so I'm personally not sure where something like 26-beta fits in terms of specific activities it would do. What do you think?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-07-31/220671542518_0d49983291e646e395f0_72.jpg" /><div class="message"><div class="username">nastya</div><div class="time">2018-03-22 11:02</div><div class="msg">well i think we need to realize how many ongoing swarms we have , what they actually deliver / timeframes / prio etc and then discuss if anyhing is missed and then create another swarm or even two for anything that is out of our radar</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-03-22 11:04</div><div class="msg">26 is a `meta` issue. We can close it since the org is more aligned with OKR?s, and swarms will be presenting progress every 2 weeks in the town hall. This will help answer Nastya?s question of how many swarms there are, what they are delivering, timeframes, priorities, etc.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-03-23 02:24</div><div class="msg">Ok, sounds good. Let's close this one for now!</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-03-23 02:26</div><div class="msg">Closing this swarm and channel for now pre previous discussions. I think #core works fine and with OKRs/more frequent town halls hopefully this will be enough. We can always re-evaluate if things change.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-03-23 02:27</div><div class="msg">@oskarth archived the channel</div></div></div><br/>
</div></body></html>
Reference in New Issue View Git Blame Copy Permalink