I love the idea of the keyboard becoming curved for one-handed typing (especially useful on the 6+). After a couple days of use, though, I was disappointed to find that the prediction isn't as good as SwiftKey's. Unfortunately, I had to switch back. Great idea though and I wish other people would adopt it!

I like that logo better, but I doubt that's their new logo. Using the Drupal Stack Exchange as an example, it appears the individual Stack Exchange sites like to tinker with the logos (the Drupal Stack Exchange logo is similar to the official Drupal logo, but not the same).

In my opinion, using commands as a form of navigation is a step backwards (moving back to the first computers, which supported only command-line navigation).

I do agree with some of the other commenters in this thread, though, that a potential area for rapid expansion with mobile devices is voice commands. I'd like to take that a step further and say that a potential area for rapid expansion would be voice commands + text interfaces that actually work.

For example, most of the text interfaces out there right now still require a very syntactic approach (Amazon's Echo is a good example, requiring you to say things in a specific way to be picked up). It'll be revolutionary once we get to a point where we can just talk to our devices, either through something like text message or voice commands, and the device can understand us and respond to our inquiries.

That, couple with the current UI design trends (simple, non-complex interfaces) creates a very nice future. You use the text apps for general everyday inquiries, and use the app with the UI when you don't feel like using text messages or voice.

The pictures gave me the impression that the conversation was actually natural (being able to type my own responses), so I downloaded it to give it a shot.

Needless to say, I was sorely disappointed to find out that the responses are canned. I was about to be incredibly impressed.

I don't see how it's possible to "rank" the various frameworks. The idea is not to create one framework that works perfectly for everything. Rather, create several frameworks that accomplish different tasks (one for iOS app development, one for Android, one for Material Design, one for a standard web app, etc). Then we can use the one that works best for the current task.

I struggle to take articles like this one seriously, and I lose respect for the sites that post them every time I see one.

Thanks for the feedback! I'll definitely add it to my notes to implement something like a "How it works" page. Will give me an opportunity to try some fancy CSS transitions too!

Thanks for the feedback! Think changing "Send mail with Snailr." to "Send physical mail with Snailr." would do the trick? Or should I make that point less subtle?

Hey guys! I was talking with a couple buddies a few weeks back, and we came up with an idea for a website that used Lob to send PDFs in the mail. Since I never have to send physical mail that often, it's always a huge pain when I have to. It'd be much easier if I could just have someone else do it for me!

I tried to go with a simple design for this site, to convey the simplicity of the product. I wanted to focus on elegant (but not too flashy) transitions in the UX, scrolling the user from one step to the other. Originally, I had planned to have only three steps, but then I found it would be easier (and more user friendly) to split all the information-getting into several steps (also verifying the information at each turn).

Let me know what you think!

By far the best implementation of Material Design I've seen so far.