2022-05-13 Developer Console Update

[OnlyOneJMJQ]

Summary

• The UI for ejecting a tutorial project is complete (Framework#148).
• We're very excited to show you alerts soon! This is an important feature for Dev Console, so we'll be gathering plenty of user feedback throughout the development process. You'll be able to:
  • Set alerts for successful or failed transactions, contract method calls, and contract events
  • Trigger actions via webhooks

ℹ️ For a quick primer on Developer Console: check out Josh's ETH Denver presentation going over it at a high level, then specifically highlighting the interactive NFT Marketplace tutorial!
_
Developer Console - Learn, Create, and Operate All in One Place
Presentation (16 Minutes) | Slides
_
Try Developer Console for yourself here.

Product Feedback

You can reach Josh Quintal with product feedback, Dev Console or otherwise, here:

Method	Josh (Dev Console & Explorer)
Calendly	30 min Timeslot
Email	josh.quintal@near.org
GitHub	@OnlyOneJMJQ
Twitter	@OnlyOneJMJQ
Telegram	@OnlyOneJMJQ
Discord	OnlyOneJMJQ#4237

Objectives & Key Results

These are our new draft objectives for this quarter. Next week we'll share final objectives including key results:

O1: Create an extensible Dev Console solution

• KR1: Create identity, integration documentation across services
• KR2: Implement minimum viable primitives for self-serve Dev Console integration
• KR3: Create framework for federated services (near-lake as case study)
• KR4: Implement org and team management

O2: Provide real-time contract data

• KR1: Event stream for attached contracts
• KR2: Alert system via email and in-app notification center

O3: Fulfill operation obligations

• KR1: Apply introspection, monitoring, ORR, devops to Dev Console
• KR2: 100% GDPR compliance
• KR3: Security (automated codebase audit, 3rd party audit, … [sync with John Smith])
• KR4: Sentry and/or FullStory
• KR5: Meet WCAG AA (or greater) accessibility standards
• KR6: 0 critical incidents originating from Dev Console

O4: Solve key technical blockers

• KR1: Key mgmt for contract interaction
• KR2: Account connection and identity

O5: Establish a consistent, scalable product process

• KR1: Implement Product -> Engineering pipeline, including documented reasoning and research for next X features
• KR2: Build council of 10 users collecting user feedback that follows users on their journey
• KR3: Expand team research efforts by X hours using external resources

Done

Product & Marketing

• @OnlyOneJMJQ: Breakdown roadmap into feature tickets
• @OnlyOneJMJQ: Final evaluation of Explorer and Dev Console relationship
• @OnlyOneJMJQ: Alerts Phase 1 product spec
  • input/output shape outlined
  • user stories
  • user research insights

Development

• @jon-lewis: Eject Tutorial - update mock service (API#45)
• @jon-lewis: Eject tutorial method (API#42)
• @jon-lewis: Fix rotate key (Framework#155)
• @jon-lewis: Update snapshot images (Framework#153)
• @jon-lewis: Users can now eject a tutorial (Framework#148)
• @calebjacob: Selected Project Refactor (Framework#147)

Doing

Product & Marketing

• @OnlyOneJMJQ: Alerts Phase 1 product spec
• @OnlyOneJMJQ: Organize and publicize future roadmap
• @OnlyOneJMJQ: Define hiring needs for this year
• @OnlyOneJMJQ: Competitive analysis to define "web3 feature parity"

Development

• @calebjacob: Research for revamped front-end components using Radix and Stitches
• @jon-lewis: Mutate SWR cache on project delete (Framework#81)
• @jon-lewis: Extract analytics calls to library to prepare for switch to segment (Framework#77)
• @jon-lewis: Gracefully handle users signing in with a different social provider than they registered with (Framework#21)
• @jon-lewis: Add unit testing (Framework#12)
• @jon-lewis: Working on implementation plan for Postgres audit tables
• @mpeterdev Implementation research for integration framework
• @mpeterdev: Rework environment variable files (Framework#11)
• @mpeterdev: Review error states for SWR fetches (Framework#6)