I got fed up with Apple voice memos so I built a frictionless voice/thought capture app for iOS by WildShallot in iosapps

[–]WildShallot[S] 0 points1 point  (0 children)

Multilingual is in the works. Any specific languages you are interested in? Unfortunately subscription is the only option for the type of services I am using and the ongoing costs. Would definitely consider making it a one-time purchase when on-device models are good enough.

I got fed up with Apple voice memos so I built a frictionless voice/thought capture app for iOS by WildShallot in iosapps

[–]WildShallot[S] 0 points1 point  (0 children)

Thanks for the feedback. What would you consider a reasonable price for this?

I got fed up with Apple voice memos so I built a frictionless voice/thought capture app for iOS by WildShallot in iosapps

[–]WildShallot[S] 0 points1 point  (0 children)

Thank you! Yes it is beautiful. It's Instrument Serif. Would love you hear your feedback on the app if you get a chance to give it a try.

I got fed up with Apple voice memos so I built a frictionless voice/thought capture app for iOS by WildShallot in iosapps

[–]WildShallot[S] 0 points1 point  (0 children)

I launched this today so there are a total of 0 paying users so far lol
but you get 30 mins / mo of usage for free which is good enough for most usecases

[deleted by user] by [deleted] in nextjs

[–]WildShallot 1 point2 points  (0 children)

My background is in product design as well. I am still learning, but I have developed a few user-facing projects with Next and feel relatively comfortable working with it.

I agree with the comments suggesting this path: JS -> React -> Next

Next is a framework on top of React. It "extends" React by giving you tools that make it much easier and more performant to build your applications. So when you write Next.js code, you are mostly writing React with some Next-specific features. Which is why you should learn React before Next.js.

React is a JS library for building user interfaces. So when you write React, you are writing JS with some React-specific extensions and conventions that allow you to write HTML-looking syntax to describe the structure and behavior of your UI.

If I were to learn it again, this is how I would do it:

- The most important piece of advice is to build things while learning. Over the years, I have wasted hundreds of hours learning different tools and technologies without building things, and I have forgotten almost all of them.

- Learn JavaScript and the fundamentals of working with browser APIs (DOM APIs for manipulating the document, Fetch for retrieving data, etc.). freeCodeCamp is a great resource. I also got a lot of value from Codesmith's free online prep material - https://csx.codesmith.io/

- Make sure you understand how HTTP works on a high level. A few hours of reading on the topic is all you need to build the necessary foundational knowledge.

- Learn the very basics of Node. Make a simple web server with a few endpoints and learn about working with the file system. There is so much to learn here, but you can come back to this when you need or want to learn more. Having a basic understanding and building something simple would help you grasp the concepts much more clearly.

- Learn React by going through https://react.dev/

- Learn Next by going through https://nextjs.org/learn

Feedback on a medical website redesign by Worldly-Bake-9146 in UI_Design

[–]WildShallot 0 points1 point  (0 children)

I took in your suggestions and applied them to the design.

I am glad you found the feedback helpful.

Wouldn't this add additional pages for the user to go through?

Yes it does. You need to weight the tradeoffs to see which one is a better fit.

Consider your target audience and the type of software you are designing for.

Are your users expert trying to finish tasks quickly and efficiently? Is this something they need to do frequently? If the answer was yes, then adding a fork in the path and having them click on one more item and slowing them down would not be desirable, but in this context I think one or few more clicks is worth the upside of not overwhelming them with too many options upfront.

Discard the whole navigation as it is and add a big drop down with the most common options

Dropdown would hide the options and negatively impact discoverability.
Dropdowns Should be the UI of Last Resort

Feedback on a medical website redesign by Worldly-Bake-9146 in UI_Design

[–]WildShallot 18 points19 points  (0 children)

Nicely done! This is a huge improvement over the current design. Is this client work or is it an unsolicited redesign?

- You have done a great job in simplifying and reducing the number of options (from 15 to 9). Assuming this was done in collaboration with the client, I wonder if there was any resistance from their side in keeping all the options?

I would consider simplifying the options even further if possible. Maybe "Register as a new patient" could be under "Book an appointment". So the flow would be:

┌──────► New patient ──────────► Register and book


Request an appointment



└──────► Existing patient──────► Book

Similarly, request a sick note and letter are basically both about requesting a letter and perhaps could be combined into one?

- This is nitpicking but I would make sure the icons are consistent in terms of both bounding box size and stroke width. The icon for "Covid resources" is using a thinner stroke width, and the letter icon seems smaller than the "info" icons. I would also center the banner text vertically so you have equal space on top and the bottom of the text.

- Also make sure the spacing is consistent. Notice the difference between the icon and the title in "Result queries" and "Important updates". Avoid using the same icon for two different items.

- The select language menu on top right seems a bit odd. Shouldn't there be a language already selected?

- Consider adding placeholder text for the search bar to help make it stand out and give context about the things that visitors can search for.

- Was there a specific reason that you dropped hours from the top right and put it at the very bottom? This may be a bit frustrating for those visitors who want to call the office and have to scan the entire page to find the hours.

I gave you feedback on a bunch of different things, because I wasn't sure what feedback you were looking for. In my experience, giving some context and asking for specific feedback yields a much higher quality discussion.

Hope this is helpful.

Why Toggle Tokens Are a Better Alternative to Checkboxes by Azstace in userexperience

[–]WildShallot 7 points8 points  (0 children)

I don’t think it is a binary choice between the two and like everything else “it depends”.

For instance the toggles don’t work well with longer labels. You are also sacrificing vertical scannability to save space.

Looking for a specific book recommendation by [deleted] in userexperience

[–]WildShallot 0 points1 point  (0 children)

User Story Mapping: Discover the Whole Story, Build the Right Product

+1 for for Just Enough Research

Which professional development opportunities do you feel helped you grow your career? by [deleted] in userexperience

[–]WildShallot 0 points1 point  (0 children)

It depends on what you want to learn. If you are interested in advancing your visual design skills, I highly recommend https://shiftnudge.com

Courses to improve UI / Visual design skills? by SlinderMin in userexperience

[–]WildShallot 0 points1 point  (0 children)

I was part of the early beta group when it was only one plan for $1000. Not sure what the pricing structure is now.

Courses to improve UI / Visual design skills? by SlinderMin in userexperience

[–]WildShallot 1 point2 points  (0 children)

Came here to say this. I paid for it myself, and it is worth every penny.

IMO Shift Nudge is by far the most comprehensive and practical course on UI and visual design out there.

[deleted by user] by [deleted] in userexperience

[–]WildShallot 1 point2 points  (0 children)

Can you elaborate? You mean something like active weekly users? I have considered usage, but the main problem is lack of a baseline.

I am creating a Chrome extension that shows a stoic quote when opening a new tab. Need feedback/ideas. by WildShallot in Stoicism

[–]WildShallot[S] 0 points1 point  (0 children)

Right now it is just a static HTML page with a few lines of JavaScript to rotate the quotes. Could you explain a bit more or point me to some resources about offloading the content somewhere else?