Status Beta by March (Dogfooding) about swarms HOT 9 CLOSED

Good stuff, thanks for this. I closed #19 as this idea to large extent replaces it with more high resolution.

@jarradh Can we please edit the requirement in section: Push Notifications & Offline Inboxing to say Offline inboxing and remove the mention of push notifications in the body. This would then reflect the specified scope of the idea. This is necessary to keep focus and scope limited for now. In the end it is very likely the resulting capability we provide turns out to have a lot of overlap (MASTERNODES!) but the specifics of the path will be delineated as we deliver a basic MVP of offline inboxing and learn more about the problem domain.

from swarms.

Great overview. Deadline is tight and scope is broad but this provide good guidance on what is essential.
In my view status-desktop, while not must have in the deliverable sense, is the main driving force behind dogfooding and will force us to have a usable product.

from swarms.

Thanks @oskarth I'm not familiar with the push notifications implementation but my understanding is that it should be another idea and integrate with offline inboxing? MASTERNODES!

from swarms.

@jarradh Correct. Once end to end MVP for offline inboxing exists / is closer to being completed we are going to specify future iterations of offline inboxing. It is likely this will include at least a mention of push notifications capability, and then we can decide specifics of where this capability lies in terms of the ideas framework.

from swarms.

@jarradh confirmed

from swarms.

@jeluard I think if Desktop is the main driving force behind dogfooding, then we have huge problems we're ignoring.

from swarms.

Quick update: Work on the beta is progressing with renewed areas of focus. I updated the main issue to reflect the latest thinking and prioritization.

from swarms.

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.

from swarms.

Not really a swarm, more of a meta issue. De facto not used. Work captured in existing swarms and OKRs help with goal alignments. Can always re-evaluate and easy to reverse.

from swarms.