glideapps / autotune Goto Github PK

• Local date-time
• Local language

See https://github.com/quicktype/autotune-server/issues/29

I should be able to start an experiment on / and complete it on /pricing.

Sorry for a pretty bike-shedding ticket, but a small improvement would be to use <auto-tune> instead of <autotune>. The latter is an unknown html element and thus invalid, but the former is a custom element, so compliant :)

If only for sanity checking

This should have a fairly aggressive timeout, or the user won't see anything until it's loaded.

We should have an 'ambient completion', especially for HTML clients.

Candidates

• Duration on page
• Scroll to bottom of page
• Click an internal link
• Submit a form

Activation

We can consider making this automatic, for example, if you don't have an autotune attribute on any links or buttons, but this still would not catch if you have aututone.complete in JavaScript somewhere.

Manual activation:

<script>autotune.autocomplete()</script>

Some websites may not have a clear completion event. It would be nice to provide an optional script that puts a small widget (e.g. NPS score, emoji reaction, stars) as an overlay that calls complete with a score.

An error occurs when printing an experiment for an app:

$ tune ls 8a77a2d6-326f-463e-baf8-ddcef1262016
...
TypeError: Cannot set property '0' of undefined
    at chunkedValue.forEach (/usr/local/lib/node_modules/autotune/node_modules/table/dist/mapDataUsingRowHeightIndex.js:49:35)
    at Array.forEach (<anonymous>)
    at cells.forEach (/usr/local/lib/node_modules/autotune/node_modules/table/dist/mapDataUsingRowHeightIndex.js:48:20)
    at Array.forEach (<anonymous>)
    at unmappedRows.map (/usr/local/lib/node_modules/autotune/node_modules/table/dist/mapDataUsingRowHeightIndex.js:39:11)
    at Array.map (<anonymous>)
    at exports.default (/usr/local/lib/node_modules/autotune/node_modules/table/dist/mapDataUsingRowHeightIndex.js:30:35)
    at Object.exports.default [as table] (/usr/local/lib/node_modules/autotune/node_modules/table/dist/table.js:126:51)
    at logTable (/usr/local/lib/node_modules/autotune/dist/cli/index.js:508:25)
    at /usr/local/lib/node_modules/autotune/dist/cli/index.js:372:25

It's not meaningful anymore, and not updated.

I load quicktype.io, refresh a few times, and the picks keep changing for a few loads, then they stick.

Hi. This service looks good. Interested to see where it goes.

I have wired it into my app. I can see the results being sent:

However tune ls 1a60c50e-xxx-c6a260848e1f does not return any results. Anything from your side?

The CLI is stuck with ES3 now.

• When starting CLI and no user is known, give an intro that says "Use signup to create a new user, or login to log in"
• Once confirmed, automatically create an app ID and link to a tutorial

I'd like to indicate when users sign up, and also when they copy code in quicktype, as separate event completions.

Refreshing a page should not produce different picks for experiments.

People expect web sites to change. We can disregard the saved state if it's older than N days. Maybe a week is a good default?

When options in the experiment are implicitly-labeled, but only differ based on text content, detect this and use the text as the label (rather than using the hash):

<autotune>
    <h1>The glass is half full</h1>
    <h1>The glass is half empty</h1>
</autotune>

import { complete, oneOf, Autotune } from "autotune-react";

const root =
  <Autotune app="5D3842F8-6811-4827-A0CC-16EB843660EB">
    <a onClick={complete}>{oneOf("CTA", ["Click me", "Click me, please"])}</a>
  </Autotune>;

Moved from https://github.com/quicktype/autotune-server/issues/14

Given the following setup:

import Turbolinks from 'turbolinks';
Turbolinks.start();

<autotune experiment="blurb">
  <p option="option-1">option 1</p>
  <p option="option-2">option 2</p>
</autotune>

<a href="#" data-autotune data-experiment="blurb">Go</a>

Steps:

1. Initial page load, option 1 is shown
2. Click on an internal link and visit page (via turbolinks)
3. Click on the initial page link, both option 1 and option 2 are visible

Would love to hear some thoughts on how to solve this!

How can we make this work with simple HTML?

One option is we gather all tags with data-experiment properties, group them by name, for each group pick one of their data-option values and hide the rest:

<p data-experiment="intro paragraph" data-option="pleasant">
  Please log in–doing so will make you fitter, happier, and more productive.
</p>
<p data-experiment="intro paragraph" data-option="threatening">
  Log in or else, you ungrateful louse!
</p>

<a href="/login" data-complete>Log in</a>

<script src="//js.autotune.io/ed019c12-1e82-4985-8940-05f524ccbcbe"></script>

Another syntax:

<at-experiment name="intro paragraph">
  <p data-option="pleasant">
    Please log in–doing so will make you fitter, happier, and more productive.
  </p>
  <p data-option="threatening">
    Log in or else, you ungrateful louse!
  </p>
</at-experiment>

<a href="/login" data-complete>Log in</a>

<script src="//js.autotune.io/ed019c12-1e82-4985-8940-05f524ccbcbe"></script>

If I was served a poorly performing pick on day 1, there's no good reason for me to get the same pick when I return on day 10.