The Non-Binary Dating App Problem Is a Form, Not a Feed
You get to the gender field on a dating app's sign-up screen — two boxes, or a dropdown that still funnels you into "man" or "woman" at the search filter three screens later. A non-binary dating app isn't the one with more words in that dropdown. It's the one where the list stops being the whole account of who you are.
That wall is the subject here: a form built for a category you don't belong to, on the way into an app that's supposed to be about you. Anketta runs its matching somewhere else entirely — not through a field you pick, but through a manuscript you write.
If you've never had to think about that field, this is what sits on the other side of it — and what changes once a product stops asking you to shrink to fit it.
Write the version of yourself no dropdown was built to holdBecause matching software needs something to sort on — a value a database can index and filter against in milliseconds. That's not a conspiracy; it's plumbing. Hard filters like age range, gender and city cut a pool of thousands down to a pool of dozens before anything smarter runs. The field was never the problem. What got loaded into it besides sorting is.
Facebook's own gender field shows how that plays out. When the company finally added a "custom" option in 2014, it arrived sitting beside the existing binary as an alternative, not a replacement — 58 options, all optional, next to two that weren't (Bivens, 2017). Longer lists read as progress. They don't, by themselves, change what the field is for.
In practice, one of three things. You pick the closest wrong answer and let it stand. You pick "other" or "prefer not to say" and hope nothing downstream treats that as a data gap to fill later. Or you write around it — in a bio, in a bracket, in a line explaining what the dropdown didn't ask — and hope a reader gets that far.
That third option rarely makes it into the conversation about dating-app design.
It's closer to universal than the industry admits. Researchers who interviewed software developers building these exact fields found that most had never been asked — by a product spec, or by themselves — whether the gender data they were collecting was necessary at all. They defaulted to asking because every other sign-up form asks, and the concrete cost of that default lands on the user: an inability to correctly gender themselves on digital forms (Bouma-Sims & Acar, 2023). The workaround people build for themselves — the bracket, the bio line, the paragraph a dropdown never had room for — is a preview of what it looks like when someone finally gets to open a blank page and describe themselves without a list at all.
A little, and mostly on the surface. Two of the platforms below expanded their own identity fields years ago, and the list genuinely grew. What didn't move at the same pace was the second, quieter field — the one deciding who actually shows up in whose results. That's the field the dropdown was never really about.
OkCupid added eight new identity terms in a single rollout in November 2014 — cis man, cis woman, transgender man, transgender woman and genderfluid among them (TIME, 2014). Two years later, Tinder partnered with GLAAD on nearly 40 auto-fill suggestions for the same field (Fortune/TIME, 2016). The discovery sort underneath it didn't move with it: users were still shown to each other as one of three categories, whatever the profile above it said (Fortune/TIME, 2016).
| Platform / update | Identity field | What still gated visibility |
|---|---|---|
| OkCupid, Nov 2014 | 8 new gender terms added in one rollout | Not documented in the same reporting |
| Tinder, Nov 2016 | Nearly 40 auto-fill identity terms, built with GLAAD | Discovery sort stayed three categories: men, women, or both |
| Anketta | No fixed identity field to expand — the manuscript is free-form, unstructured text | Hard filters (age, gender, "show-me" preference, intent, city) route visibility, kept separate from anything written |
Not by itself. A list can grow from two entries to fifty and stay a list — a fixed, enumerable, queryable set of values, which is exactly the property that made it useful for sorting in the first place. The tension doesn't disappear when the list gets longer. It just takes more scrolling to find where your answer still isn't.
This is the part most "best non-binary dating apps" roundups skip, because counting dropdown entries is easy and reading the schema underneath them isn't. A field built to be filtered on will always draw a line somewhere, however far you push it. The fix was never a longer list. It was never asking one field to do two jobs at once.
Anketta still asks the practical questions at sign-up — age, gender, a "show-me" preference, city — because a matching system needs a pool to filter before anything smarter runs on it. What it doesn't ask is for those same answers to double as your self-description. That job sits somewhere else entirely: the manuscript, free-form text with no fixed prompts and no length requirement, organized into headings and paragraphs however you choose to organize them.
The matching itself runs on what actually got written. A reader underlines a phrase they respond to, and the system surfaces more writing like it — the same text-based mechanism whether the phrase sits next to a name that fits a dropdown cleanly or one that never did. Nobody's compatibility with you gets computed from the box you checked. It gets read. There's no photo attached to any of it before a match either — matching runs on the writing alone, which our guide on dating without photos covers in full.
If the last dropdown you filled out felt like a guess, this is what writing instead of guessing looks like.
Open the editor and describe yourself in your own words, not someone else's field namesOn most apps, less easily than the sign-up flow suggests. A field you picked once often becomes a field you have to delete and remake to change, and some products treat a changed gender answer as grounds to reset an account's trust or verification status — even though nothing about the person changed, only an entry in a database. None of that is inevitable. It's a design choice a form makes for you before you've met anyone.
A short list worth checking against any sign-up form, non-binary or not:
- Is the field that describes who you are the same field the app uses to decide who sees you — or are those two different things?
- Can you change your answer later without starting the account over?
- If you pick "other" or leave it blank, does anything in the product tell you where that answer actually goes?
None of the three questions are complicated. Almost nothing about a signup form ever is — which is exactly why the industry has had two decades to get them right and mostly used that time widening a dropdown instead. You can write it out for yourself rather than take the form's word for what the answer should have been.
What is a non-binary dating app?
In practice, an app that doesn't need one gender answer to do two jobs at once — sorting your visibility to others and describing who you are. Most platforms still use a single field for both, which is where the friction comes from. A handful, Anketta included, split the two: a coarse filter for visibility, free-form writing for everything else.
Does Anketta ask users to pick a gender at sign-up?
Yes — gender is one of several practical filters, alongside age, a "show-me" preference and city, applied before any deeper matching runs. It exists to narrow who you're shown, not to summarize who you are. Self-description happens separately, in the manuscript you write, which carries no fixed fields at all.
Why do so many dating apps still sort search results into just two categories?
Because the discovery mechanism and the identity field are usually built as two separate systems, shipped years apart. Updating a dropdown is a smaller project than rebuilding how matching routes visibility underneath it. Facebook and Tinder both expanded their identity lists well before touching the systems that decided who actually got shown to whom.
What's the real difference between a "custom" gender field and a free-text one?
A "custom" option is still an enumerable list, just a longer one — choose from fifty instead of two, and the software still stores a value it can query. Free text isn't a bigger list; it isn't a list at all. Nothing downstream can filter on prose the way it filters on a field, which is a limitation and, here, the entire point.
Does a longer list of gender options make a dating app better for non-binary daters?
Not on its own. A longer list is evidence a company revisited the field at some point, which counts for something. It says nothing about whether that field still doubles as the mechanism deciding who sees you — and that doubling, not the list's length, is what was actually broken.
Can I change how I described myself after I've already signed up?
It depends entirely on the app, and it's worth checking before investing time in a profile — or a manuscript — you might want to revise later. A field with a fixed list is usually a quick edit. A field tied to trust or verification status sometimes isn't, and that's a property of the specific product, not something inherent to asking the question at all.
A dropdown only ever asks which box to check; the jacket still needs someone to get the cuff right before they walk out the door.
Unsure about writing? Try reading first.