1288711 - (Activity Stream) Validating early prototypes

Status: RESOLVED FIXED

(Firefox for Android Graveyard :: General, defect, P1)

Description

[Sebastian Kaspari (:sebastian; :pocmo)]

How can we validate early prototypes?

On desktop we have test pilot - what do we do on mobile (Android)?

What we have right now and what we have been using in the past:
https://docs.google.com/document/d/12yuRKdu_C1nkw3RIP0xJRmBTIGmNbOyRis6TRm3wZmY/edit

Additional questions:
* Can we avoid being slowed down by the release trains?
* Can we have users opt into the new experience regardless of release channel?

Comment 1

[Sebastian Kaspari (:sebastian; :pocmo)]

Looking at and evaluating some of the ideas here: https://docs.google.com/document/d/1__Cou4YLyS1dAL7pPbqlBXhG6LvTL_XYJb88aFM6VjY/edit

Comment 2

[Sebastian Kaspari (:sebastian; :pocmo)]

Attachment: Activity Stream Add-on on Fennec

To evaluate rendering activity stream as web content I patched the activity stream add-on to run on Android. It kind of shows some UI but doesn't render any data.

This might work for the core "new tab" page but some of the mocks are showing and modifying UI outside of the tab/web content. This is something we can't do easily (or at all) with an add-on right now. As soon as we have to ship additional APIs we need to ride the release trains again.

Comment 3

[Sebastian Kaspari (:sebastian; :pocmo)]

Attachment: React Native integration into Fennec

This is a screenshot of a react native integration into Fennec (the red thing).

Comment 4

[Sebastian Kaspari (:sebastian; :pocmo)]

I move this back to the backlog and work on highlights first (bug 1293710).