There's no reason for both the story count and the story summary to be clickable. It's confusing because:

(a) It's not clear what the number in parentheses even means (until you click and infer)

(b) Separate links makes you think they lead to different pages

Also, echoing another comment, it's not really clear what "incoming" and "outgoing" stories mean. Maybe "new" vs. "stale"?

Except not:

> The interface design has drawn criticism from privacy advocates, as the large black "Accept" button is prominently displayed while the opt-out toggle appears in smaller text beneath. The toggle defaults to "On," meaning users who quickly click "Accept" without reading the details will automatically consent to data training.

Definitely happened to me as it was late/lazy.

Comments URL: https://news.ycombinator.com/item?id=43850550

Points: 68

# Comments: 22

I think my confusion with clue 2 was that I had never heard of the idiom "[to] fish or cut bait" [1]

[1] https://en.wikipedia.org/wiki/Fish_or_cut_bait

- Without the tutorial, it's confusing that you're not supposed to click and you're supposed to start typing. I wonder if placing the text box at the top would make that more clear.

- Some of the clues are confusing due to inconsistent punctuation. For example:

  [to ___fish, to lure someone in using a fake internet persona] = cat
  [do this or cut bait] = fish
  [taking a pay one is a bummer] = cut
  [rocks when added to soda will NOT cause your stomach to explode] = pop

What we need are designers who can help establish a foundational structure (information architecture) that leads to discoverable and simple UIs to nudge users in the right direction. Once users are at a place where they know what’s possible/available, then perhaps you can allow some fuzziness to help them cross the line to accomplish their task.

[1] https://www.interaction-design.org/literature/topics/discove...

Well that’s your first problem. Unless you’re using corporate email?

> `1.0` books (?) – Martin Ba Commented May 22, 2024 at 13:3

:)

Perhaps the grandparent comment of mine did, not me.

> We'll add something back to the FAQ on this, thank you all for pointing it out.

So people don't read onboarding instructions, but you're going to bury the pricing info in an FAQ in the App Store where it's hidden below the fold?

The fix is quite easy. Here's a redesign for your in-app registration screen:

   Create account   
                    
  ┌────────────────┐
  │Name            │
  └────────────────┘
  ┌────────────────┐
  │Email           │
  └────────────────┘
  ┌────────────────┐
  │Password        │
  └────────────────┘
                    
    ┌────────────┐  
    │  Register  │  
    └────────────┘  
   7-day free trial,
    $6.67/mo after

Edit: The "dark" pattern is in the registration flow. It doesn't mention that the app requires a subscription anywhere until after you've created an account. Surely you could add a disclaimer before creating your account? This has nothing to do with the App Store.

Edit 2: I'm not saying you intended to implement a dark pattern. Just perhaps a UX oversight.

Edit 3: The download page would be another great place to put this info, since that's the primary CTA on the home page (there's 4 prominent download buttons).