CiteIt.net

Building trust in media

Substack Beta-testing

by

Where to find Early Adopters?

Thus far I’ve attempted to get local and national newspapers and magazines to adopt CiteIt’s contextual Citations with little success.

I have hopes that Substack may be a better fit because Substack is a startup and its writers are more likely to be early adopters or independent-minded.

Despite the fact that Substack may be an early adopter, I still think it would be wise to create a stronger pitch by first testing the idea with writers and see if I can assemble a list of Substack writers who are interested in becoming beta testers.

1) WordPress Demo #

Beta testers don’t need to try the WordPress app if they don’t have time, but they do, they can get an idea how CiteIt currently works on the Demo site.

The WordPress demo adds 2 buttons to the editor as shown in the following video.

Password: demo22

 

Only for the curious:

This WordPress App “unpolished” but gives you an idea how the feature could work on Substack.

I’m not expecting “beta testers” to try the WordPress unless they are curious and have time.

2) Expectations for the Beta test: #

Beta testers would:

  1. Use the CiteIt and evaluate how easy it is to use.
  2. Evaluate whether contextual citations are useful and suggest improvements.
  3. Report any bugs they find.

 

3) Technical Details:  (you can skip the rest of  this page) #

I would expect the beta test to add 2 buttons to the Substack editor, similar to the WordPress Demo I created.

  1. At first, the goal would be to test whether the contextual citations concept is useful and get a sense of how much programming time would be involved in creating the first version.
  2. If writers like the concept, I expect that Substack would want to rewrite the code in JavaScript (rather than Python) to better integrate with the rest of their codebase.
  3. After Substack has developed the initial code, beta testers would then use it in their writing and report bugs in Substack’s code, until the point at which Substack is happy that the feature is working well enough to go live.

How Substack handles beta-test signups: #

Here’s an example of how Substack currently gives writers the option to signup to beta-test a feature. This is their “video” beta test signup:

Beta Test Application

I expect that this process would only begin after Substack has expressed interest in going forward with this feature.

So for now, I’m merely informally gathering a list of writers who are interested in CiteIt so that I can make a stronger case that this feature is worth considering.

Usability Testing CiteIt: First Series

by

Usability expert Jakob Neilson said that most of the lessons you get from usability testing can be obtained from only 5 users.

Some people think that usability is very costly and complex and that user tests should be reserved for the rare web design project with a huge budget and a lavish time schedule. Not true. Elaborate usability tests are a waste of resources. The best results come from testing no more than 5 users and running as many small tests as you can afford.

Long term plan: multiple series of tests

He recommends doing iterative testing, using 3 studies:

The curve clearly shows that you need to test with at least 15 users to discover all the usability problems in the design. So why do I recommend testing with a much smaller number of users?

The main reason is that it is better to distribute your budget for user testing across many small tests instead of blowing everything on a single, elaborate study. Let us say that you do have the funding to recruit 15 representative customers and have them test your design. Great. Spend this budget on 3 studies with 5 users each!

 

I’ve just finished my first series of usability tests with 7 users:

  1. Arwen: 40s
  2. Susan: 60s
  3. Andrew: 60s
  4. Ken: 70s
  5. Marilyn: 70s
  6. Harold: 70s
  7. John: 80s

 

This first round of testing I focused on retirees because:

  1. They are more likely to have an extra one+ hour to dedicate towards the testing process
  2. They are more likely to discover the types of problems that affect many older readers, which is a big demographic for newspapers and other media.
  3. If a desktop design works for older users, it likely works for younger users who use desktop.

 

Next Phase:

Two of my first round users tested mobile and two tested phone.  The second phase of testing should better test mobile devices.

 

How I Tested:

1) Reading:

I directed users to a testing page and gave all users 2 articles to read without instructing them on how they should read the articles.

There instructions were to read them as they usually would and narrative what they are thinking as I watched over their shoulder.

Lesson (Reading):

I found that some users are wary of viewing videos.  One problem I observed is that when a user clicks on a video, they may not be able to tell whether the video is about to play or whether they need to click again.

Sometimes the first click only selects the video and a second click is required to play the video.  But sometimes the player is buffering and they click a third time, which causes the player to pause, rather than play.

I plan to solve this problem by creating a dedicated “play” button.  The “play” button will change to a “pause” button when the button is pressed or when the video is pressed.  This requires the OnChange event to recognized the players state and toggle the state..

2) Writing:

I also had most of them test the process of creating new citations using the WordPress demo area.

Lesson (Writing)

My oldest user (in their 80s) was able to do the reading, but not the writing, because it requires the ability to copy text from one tab and navigate and paste into the WordPress tab.

This is no different than the requirement for making a link in WordPress, but needs to be named as a limitation.