🧠 All had strong knowledge of Wikifunctions and Abstract Wikipedia

📐 All had strong understanding of what a function does

Page 1:

• UX
  • ✏️ "I hope there is a check that the function already exists"
    • Expects there to be search for a function as he is typing a name
  • ✏️ Some confusion around what step in the sub-navigation he is on
    • Doesn't understand what "start function" means here
  • ✏️ Needs guidance for how they can style the function case
  • ✏️ Alias is for people looking for functions — explain why it matters in the copy
  • ✅ Understands what an alias is — calls it a "synonym"
  • Considers diverse examples for names and aliases
• Mental model
  • Does not want to start from scratch. "You don't want to have the cold start problem".
    • Had expectations around integration with Wikidata and references it deeply
• UI
  • Many people were distracted by the right arrow in the yellow sidebar
  • "Wikifunctions function" is repetitive
• ✅ Understood aliases correctly ... called them synonyms
• ✅ Understood the screen correctly
• Interested in multilingual aliases

Page 2:

• UX
  • ✏️ Itching to implement
  • ✏️ Confused by text under the title being the same and not updating with the next step
    • Had some confusion around which step he's on
    • Confused by blue check mark to indicate the page he is on
  • Some confusion around adding additional inputs versus multilingual labels
• Mental model
  • Would I not always want the input label to be the same as the type?
    • —> Not sure he understands what the input label is for (maybe rephrase as argument label?) (or parameter or variable name... Amir also says this)
  • "In other programming languages and other Wiki templates, these are called arguments or parameters"
• UI
  • It would be nice to see the input labels next to the name of the function
    • I would like to see the main name of the function on this page
      • Forgot what function he was writing
      • Did not notice function name or diagram on the right
  • Input labels don't have descriptions so once the text box is inputed it won't be clear what that box is for
  • Input selector looks inactive
• ✅ Understood the screen correctly

Page 3:

• UX
  • ✏️ "Maybe don't need the lengthy process"
  • ✏️ Save and write implementation - worried that proceeding to implementation without clearly saving
    • Had concerns around work being saved
  • ✏️ Is there a way to download the draft?
• Mental model
  • "Called return value in modern languages"
  • "We usually don't have the write button in media wiki"
  • "I guess that write is the same thing as publish?"
  • I would expect to see a summary of my function after I hit save
    • Similar mental model to Wikipedia
  • Clicks for him at the very end!
• UI
  • Puzzled by "input(s)" plural but single output
  • "This page looks a bit empty"
  • Finds the visualization "very nice"
• ✅ Understood the screen correctly

Overall:

• UX
  • ✏️ Had difficulty knowing which data type to give the output
    • 💡**Opportunity for providing feedback. What if they select the wrong datatype?**💡
  • ✏️ Have all four steps in one screen — for more efficiency (expert mode)
  • ✏️ "Quite edit mode —> type in the yellow visualization"
  • Comfortable starting place for getting started with building a function
  • Was not ****irritated by the experience
  • Described interface as clean, clear, easy to understand (3)
  • Matched expectations
  • Was curious about the mobile experience (2)
  • Noticed the parallelism between left and right side of screen
  • "Relationship between left and right side of screen was helpful" ... parallelism was nice... diagram on the right is essentially a glorified progress bar
  • Noticed the diagram immediately (recurring theme)
  • ✏️ Wants to tab between the global navigation —> 💡Let them explore/encourage it💡
  • Likes the order of steps needed for a function to be run.
  • ✏️ Tester's understanding is that without testing there would be no function
  • Suggestion: Using mental model of "defining function" over "creating function"
  • ✏️ Suggestion: Not clear for me how someone hands off a function if they cannot write the implementation — make the interface and the environment collaborative
  • Successfully gave function name (3)
  • Successfully adds an alias (2)
  • Successfully adds the correct input type (3)
  • Successfully adds output type (4)
• ✏️ Mental model
  • Extremely knowledgeable of Wikifunctions, has lots of context
    • Mentions Wikifunctions as connected to Wikidata / references Wikidata several times
  • References Wikidata and Abstract Wikipedia several times
  • ✏️ They think the implementation needs to be emphasized — function can't be used until it is implemented
• UI
  • Suggestion: I expect to see the work I did when I am on the coding page
  • Very closely read the copy under Create a function
  • Noticed the sub-navigation second
  • Suggestion: Explain the data types in the dropdown menu
  • Suggestion: Try changing UI for alias — multiple bubbles in the same box
• Important that the interface is multilingual

✏️ Quotes

• "It looks familiar to Wikipedia, but a bit more polished or modern"
• "I was very easily able to create a function"
• "Quite frankly, I would not make a function without trying to implement it myself"
• "A function needs some basics to be saved"
• "At this speed it is easy to create a function"
• "The sub-progress was not clear to me initially but became clear pretty quickly"