3 ms·

Very important thing missing: a demo form, to understand the user experience. Especially if you’re comparing yourself with Typeform, which is rather controvers

Very important thing missing: a demo form, to understand the user experience. Especially if you’re comparing yourself with Typeform, which is rather controversial. (I detest its entire approach.)

wouldbecouldbe 1y ago
I see a demo form if you click on the demo, but it's not very obvious
- preetsuthar17 1y ago
  still if you want to try the demo you can try here https://www.ikiform.com/forms/a2675039-5901-4052-88c0-b60977d3d048 https://www.ikiform.com/forms/a2675039-5901-4052-88c0-b60977...
  - chrismorgan 1y ago
    OK, initial feedback: you need to work on your colours and contrasts. Disabled Previous button isn’t clearly disabled, placeholder value looks almost the same as an actual value, focus indicator is too subtle. I reckon these things are noticeably harder to get right on dark than on light colour schemes. Also keyboard navigation is poor: when you shift to a new page, you should probably focus the first field; or at the very least reset focus to the start of the document so that when the user presses Tab after having clicked the Next button they get to the first field, not the footer “Powered by Ikiform” link. (This doesn’t affect pressing Enter from one of the inputs—when they disappear, focus shifts back to the top.) But I’m pleased to say that it’s nothing like Typeform. I strongly recommend ditching any comparison with it, you’re doing things sanely, unlike their experience.
  - pbronez 1y ago
    It’s a nice form. On iOS when I hit next it didn’t pop me up to the beginning of the next page. Agree with the sibling that it would be nice to get focus on that next obvious step.
  - RandomBacon 1y ago
    The name fields have a minimum length of two characters. There are people with single character names.
    - bornfreddy 1y ago
      Mandatory reading for anyone implementing forms with names: Falsehoods Programmers Believe About Names [0]. [0] https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-...
      - librasteve 1y ago
        Thanks for the link … great read and yes very tricky. I have started hacking a bit on a Contact::Name text parser in raku Grammars if anyone would like to check it out - contributions are very welcome! https://raku.land/zef:librasteve/Contact https://raku.land/zef:librasteve/Contact Why Raku? - the easy built in Grammar syntax means that coders can work quickly to build structured parse trees that can deal with all the textual nuance (unicode, language, rtl, pluggable sub-grammars…) - the consistent ecosystem provides for class / roles as first class packages in their own right, so we can have a shared standardized tree of real word objects we want to parse out of text such as LLM responses
preetsuthar17 1y ago
I was actually working on the demo and adding it in the home page
nikolayasdf123 1y ago
yeah, looks like animations between pages is lacking. as well as just animatinos in general
- Jaxan 1y ago
  I didn’t notice they were lacking. Are animations really asked for by users?
  - MajimasEyepatch 1y ago
    They're not explicitly asked for, but everywhere I've worked that's tested them has found that they improve conversion rates.
    - nikolayasdf123 1y ago
      +1. users don't ask such things. they can't formulate them in writing (unless they are designers, artists, visual editors, UX experts themselves) and don't have time for that
  - nikolayasdf123 1y ago
    do your follow any design guideline? what's your design principles? I recommend picking some (e.g. Apple: https://developer.apple.com/design/human-interface-guidelines https://developer.apple.com/design/human-interface-guideline...), and try to match that. there has been lots of though put into it, good to reuse before you came up with your own.

Very important thing missing: a demo form, to understand the user experience. Especially if you’re comparing yourself with Typeform, which is rather controversial. (I detest its entire approach.)

wouldbecouldbe 1y ago

I see a demo form if you click on the demo, but it's not very obvious

preetsuthar17 1y ago
still if you want to try the demo you can try here https://www.ikiform.com/forms/a2675039-5901-4052-88c0-b60977d3d048 https://www.ikiform.com/forms/a2675039-5901-4052-88c0-b60977...
- chrismorgan 1y ago
  OK, initial feedback: you need to work on your colours and contrasts. Disabled Previous button isn’t clearly disabled, placeholder value looks almost the same as an actual value, focus indicator is too subtle. I reckon these things are noticeably harder to get right on dark than on light colour schemes. Also keyboard navigation is poor: when you shift to a new page, you should probably focus the first field; or at the very least reset focus to the start of the document so that when the user presses Tab after having clicked the Next button they get to the first field, not the footer “Powered by Ikiform” link. (This doesn’t affect pressing Enter from one of the inputs—when they disappear, focus shifts back to the top.) But I’m pleased to say that it’s nothing like Typeform. I strongly recommend ditching any comparison with it, you’re doing things sanely, unlike their experience.
- pbronez 1y ago
  It’s a nice form. On iOS when I hit next it didn’t pop me up to the beginning of the next page. Agree with the sibling that it would be nice to get focus on that next obvious step.
- RandomBacon 1y ago
  The name fields have a minimum length of two characters. There are people with single character names.
  - bornfreddy 1y ago
    Mandatory reading for anyone implementing forms with names: Falsehoods Programmers Believe About Names [0]. [0] https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-...
    - librasteve 1y ago
      Thanks for the link … great read and yes very tricky. I have started hacking a bit on a Contact::Name text parser in raku Grammars if anyone would like to check it out - contributions are very welcome! https://raku.land/zef:librasteve/Contact https://raku.land/zef:librasteve/Contact Why Raku? - the easy built in Grammar syntax means that coders can work quickly to build structured parse trees that can deal with all the textual nuance (unicode, language, rtl, pluggable sub-grammars…) - the consistent ecosystem provides for class / roles as first class packages in their own right, so we can have a shared standardized tree of real word objects we want to parse out of text such as LLM responses

preetsuthar17 1y ago

I was actually working on the demo and adding it in the home page

nikolayasdf123 1y ago

yeah, looks like animations between pages is lacking. as well as just animatinos in general

Jaxan 1y ago
I didn’t notice they were lacking. Are animations really asked for by users?
- MajimasEyepatch 1y ago
  They're not explicitly asked for, but everywhere I've worked that's tested them has found that they improve conversion rates.
  - nikolayasdf123 1y ago
    +1. users don't ask such things. they can't formulate them in writing (unless they are designers, artists, visual editors, UX experts themselves) and don't have time for that
- nikolayasdf123 1y ago
  do your follow any design guideline? what's your design principles? I recommend picking some (e.g. Apple: https://developer.apple.com/design/human-interface-guidelines https://developer.apple.com/design/human-interface-guideline...), and try to match that. there has been lots of though put into it, good to reuse before you came up with your own.