Chrome removed the green padlock as a way to show the its secured by default. Therefore, an error will show when it's not https. Could the author please explain why that is bad?
I don’t use Chrome on iOS but Safari explicitly shows “Not Secure” for a non-HTTPS site. The secure ones have a padlock. My non-tech friends find this to be very clear; they have learned not to enter information when a website is “Not Secure”.
If this is the direction in which Chrome is heading, the 5-billion or so users will know, without a doubt, whether a site is secure or not. I don’t see a problem with this change, per se. The others, especially targeting ad blockers, seem to be a step in the wrong direction.
How would you know if they removed icon for non-safe sites.
You wouldn't as there is no indication of that anywhere
(no http string in address, no icon indication).
This brings unnecessary bit of burden to user who would have to pause to make sure site is safe (bank, etc).
That is a bit like trying to strip 'not occupied sign from public toilet stall. Claiming that if its occupied appropriate sign will be displayed.
Say you want to use a stall and you couldn't see a sign if its free or not, that will give u a small pause before you 'try' one.
I understand where you coming from. However, would the patient know if machine is functioning correctly if it is silent? What happens if it's not plugged in correctly?
I'm a Toastmasters member, and one of the things I learned with presenting technical talks is that you should know your audience. If your audience understands the tech, then speak at a technical level, otherwise speak at a very high level
What exactly do you want a link to? I just used my friend's old maths books from high school (he did all 7 courses available, which means about 25% of his 3 year HS studies. It includes stuff like linear algebra and linear optimization and game theory. ) and lots of time.
He went on to become a PhD in maths and just pointed me in the right direction when I couldn't figure stuff out myself.
Good luck! Let me know if you give it a try, and if you think of anything that could be added/improved. Having the data has been so incredibly help for me and my wife.
I strongly urge you to make a mobile version - it's much easier to enter data on the go, rather than having to walk over to your computer. UX is going to be key here - dropdowns are hard, buttons are easy.
Yeah, I really would have liked to make it an app with better handling of offline data and such. But I simply didn't have the setup or experience to approach it that way by the time I decided to start (I think a month or so before our son was born).
On the plus side, the current app does have a pretty solid (I think!) mobile UI. When in mobile, there is a special one-click button for starting a timer and bigger "quick add" dropdown for entries. I actually have been meaning to add a mobile version screenshot to highlight the fact that it is pretty functional on mobile (with the caveat that it needs an Internet connection). Mobile is how my wife and I use it about 95% of the time and has been a huge driver in my development of the UI.
> When in mobile, there is a special one-click button for starting a timer and bigger "quick add" dropdown for entries.
Nice! I didn't check it out on mobile.
I'm incredibly impressed, btw, that you're working on something like this with a newborn. The month before and after birth, I was basically dead to the world. Kudos to you and her!
All those kudos can go to my wife. She was incredibly supportive of giving me time to work on this before the birth and tweak it after. We also had lots of good support from her family. Definitely would not have happened without that.
I'm currently working for a company where the our manager holds a tight grip against the code we write, but he doesn't seem to guide us in the correct direction.
