[G2bb]

Will there be a beta testing program for BLOCKS. Maybe get a watch a month or so before official launch to test it and work out bugs. After maybe they could test software features before they're released to the public. It might also be cool to have a list of "Beta Users" available to developers to allow them to test updates to a block or even test a block before it is released to the public. That part would of course be up to the developer if they want beta testers.
Just a though.

[Snyper493]

This sounds like a really good idea. It would make sense to do something like this with how much work that has all ready been done. It gives the select few to look it over and test any possible software and hardware issues that might arise in the first few weeks of having it. And it would also allow them to make short, quick tutorials on changing out modules with ease for the team.

[Fuwo]

I will just throw my thoughts about this in here.
First it would need to be an open system, so everyone who is interested could enter so the (lets call it) "beta-pool" would offer a wide variation of users. Then (the private data security fans will not like this part) it would be necessary to collect some information about the beta-pool users. For example which modules they already own and which modules and functionalities they would be interested in, which apps there using often, what functionalities of which modules they using, and of course some general user information like age, gender, job, education etc.

And after building this beta-pool developers would have the opportunity to distribute their apps/module that should be tested to the people who would actual use them.

just random examples:
a app that gives you voice input/search and result output for wolframalpha would be mainly distributed to professors, scientists, mathematicians, students etc.

A hiking planing app with weather forecast, offline map, viewpoint advises and calendar access to plan this trip would be distributed to people who love hiking and more particularly to people who have the adventure, heart rate and/ore GPS module.

Well, as I said, just my first thoughts and ideas...

[Seyi Agboola]

(02-01-2016, 04:22 PM)G2bb Wrote:  Will there be a beta testing program for BLOCKS. Maybe get a watch a month or so before official launch to test it and work out bugs. After maybe they could test software features before they're released to the public. It might also be cool to have a list of "Beta Users" available to developers to allow them to test updates to a block or even test a block before it is released to the public. That part would of course be up to the developer if they want beta testers.
Just a though.

I think we will eventually have some kind of beta testing but not sure what form it will take. I would assume, our BLOCKS members who paid $50 deposits a year ago would be first in line, along with developers via SDKs followed by a very small few of the most enthusiastic fans. We can review this a lot closer in the coming months

[Seyi Agboola]

(02-01-2016, 07:29 PM)Fuwo Wrote:  I will just throw my thoughts about this in here.
First it would need to be an open system, so everyone who is interested could enter so the (lets call it) "beta-pool" would offer a wide variation of users. Then (the private data security fans will not like this part) it would be necessary to collect some information about the beta-pool users. For example which modules they already own and which modules and functionalities they would be interested in, which apps there using often, what functionalities of which modules they using, and of course some general user information like age, gender, job, education etc.

And after building this beta-pool developers would have the opportunity to distribute their apps/module that should be tested to the people who would actual use them.

just random examples:
a app that gives you voice input/search and result output for wolframalpha would be mainly distributed to professors, scientists, mathematicians, students etc.

A hiking planing app with weather forecast, offline map, viewpoint advises and calendar access to plan this trip would be distributed to people who love hiking and more particularly to people who have the adventure, heart rate and/ore GPS module.

Well, as I said, just my first thoughts and ideas...

For initial thoughts, this is very well thought out. Essentially you are right in that different modules require more thorough testing to uncover any bugs and perfect the end user experience across all our wearers.

[G2bb]

(02-01-2016, 07:29 PM)Fuwo Wrote:  I will just throw my thoughts about this in here.
First it would need to be an open system, so everyone who is interested could enter so the (lets call it) "beta-pool" would offer a wide variation of users. Then (the private data security fans will not like this part) it would be necessary to collect some information about the beta-pool users. For example which modules they already own and which modules and functionalities they would be interested in, which apps there using often, what functionalities of which modules they using, and of course some general user information like age, gender, job, education etc.

And after building this beta-pool developers would have the opportunity to distribute their apps/module that should be tested to the people who would actual use them.

just random examples:
a app that gives you voice input/search and result output for wolframalpha would be mainly distributed to professors, scientists, mathematicians, students etc.

A hiking planing app with weather forecast, offline map, viewpoint advises and calendar access to plan this trip would be distributed to people who love hiking and more particularly to people who have the adventure, heart rate and/ore GPS module.

Well, as I said, just my first thoughts and ideas...

I like this idea, I hadn't thought about collecting all this information and from a developer's standpoint it would make the feedback you receive from the beta testers you select more relevant.

[Neil Shah]

(02-02-2016, 10:16 AM)Seyi Agboola Wrote:  

(02-01-2016, 04:22 PM)G2bb Wrote:  Will there be a beta testing program for BLOCKS. Maybe get a watch a month or so before official launch to test it and work out bugs. After maybe they could test software features before they're released to the public. It might also be cool to have a list of "Beta Users" available to developers to allow them to test updates to a block or even test a block before it is released to the public. That part would of course be up to the developer if they want beta testers.
Just a though.

I think we will eventually have some kind of beta testing but not sure what form it will take. I would assume, our BLOCKS members who paid $50 deposits a year ago would be first in line, along with developers via SDKs followed by a very small few of the most enthusiastic fans. We can review this a lot closer in the coming months

I hope that includes me

[Peter]

(02-01-2016, 04:22 PM)G2bb Wrote:  Will there be a beta testing program for BLOCKS. Maybe get a watch a month or so before official launch to test it and work out bugs. After maybe they could test software features before they're released to the public. It might also be cool to have a list of "Beta Users" available to developers to allow them to test updates to a block or even test a block before it is released to the public. That part would of course be up to the developer if they want beta testers.
Just a though.

That would be awesome indeed!

Quote:Compared to our phones, smartwatches are small and have limited space inside. This means that other smartwatch companies are having to compromise on which features they to put into a tiny little device that fits around your wrist. We wanted to give that power back to you, the user, to choose what features are important just for you.

Blocks said that they will make watches that are personal to people.
So by giving each kind of person a test watch, with some information like @Fuwo said, then Blocks can get very accurate test reports.

[a_guy]

I think the order is right: first members, then developers that will provide debugging and that can lead the new modules then the most enthusiastic fans who will provide feedback on real consumer usage. It is important to have all kinds of peoples to try it out before launch. Developers will use it to create new things or to correct bugs while users will help to understand the real usage of the BLOCKS smartwatch.

[G2bb]

(02-02-2016, 03:39 PM)a_guy Wrote:  I think the order is right: first members, then developers that will provide debugging and that can lead the new modules then the most enthusiastic fans who will provide feedback on real consumer usage. It is important to have all kinds of peoples to try it out before launch. Developers will use it to create new things or to correct bugs while users will help to understand the real usage of the BLOCKS smartwatch.

Personally I think Ambassadors should have the same rights to the first wave of beta as members. Being a part of both groups has shown me that both members and ambassadors have the same amount of passion for BLOCKS and they both deserve a heightened chance at beta. That's just my 2 cents though.