Reply to thread

Message

<blockquote data-quote="Weasel" data-source="post: 464738" data-attributes="member: 9520">Looks good, got a few ideas and feedback points.<ul>
<li data-xf-list-type="ul">I agree with the above, and I would also not fire off a new request for every key on page load. If you structure the API right, you can do one request to fetch them all, and if you want one specifically, define the type in the GET parameter (like /api/v1/keys/wordpress for a specific one, or /api/v1/keys to return them all).</li>
<li data-xf-list-type="ul">Maybe let people favorite their types of keys, store them locally, and put favorites on top.</li>
<li data-xf-list-type="ul">Give the cards an info button (something small, top right corner or something within the card an &quot;I&quot;), and provide information about the type of key, where they can put it, etc. Just adds some extra content, and can also be good for SEO.</li>
<li data-xf-list-type="ul">Add a compact view, where you can get rid of the images and show a table with the type of key and the value, and the copy/refresh buttons. Some people like a compact overview, UX is key, and giving users choice is a good way to go.</li>
<li data-xf-list-type="ul">Add a suggestion box for people who want to see some kind of key added.</li>
<li data-xf-list-type="ul">Open Source the code. People want to know how the keys are generated to make sure they are safe. Linking it to your GitHub also gives people the ability to open up pull requests and add keys they think are missing themselves, or they can open an issue.</li>
</ul>I like the design and simplicity, though.</blockquote>

[QUOTE="Weasel, post: 464738, member: 9520"] Looks good, got a few ideas and feedback points. [LIST] [*]I agree with the above, and I would also not fire off a new request for every key on page load. If you structure the API right, you can do one request to fetch them all, and if you want one specifically, define the type in the GET parameter (like /api/v1/keys/wordpress for a specific one, or /api/v1/keys to return them all). [*]Maybe let people favorite their types of keys, store them locally, and put favorites on top. [*]Give the cards an info button (something small, top right corner or something within the card an "I"), and provide information about the type of key, where they can put it, etc. Just adds some extra content, and can also be good for SEO. [*]Add a compact view, where you can get rid of the images and show a table with the type of key and the value, and the copy/refresh buttons. Some people like a compact overview, UX is key, and giving users choice is a good way to go. [*]Add a suggestion box for people who want to see some kind of key added. [*]Open Source the code. People want to know how the keys are generated to make sure they are safe. Linking it to your GitHub also gives people the ability to open up pull requests and add keys they think are missing themselves, or they can open an issue. [/LIST] I like the design and simplicity, though. [/QUOTE]

Verification

Reply to thread

Connect with us

Newest members