maitrik

Hey we may have something like this. Can you please email me at maitrikvk [at] newtonhq [].com . Would love to have a chat.

Glad you found this useful! :) Half-screen flyout menus has the power to beat thumb accessibility challenges.

We are working on adding more Android apps for sure. Curating the app gallery is a huge undertaking. One app takes around 1-2 days. Its definitely on our to-do.

Not sure why you are being downvoted. I agree with you. :) Still fixing all these. And you are correct it is a bit slower due to HN front page.

Hey that does seem a bit strange. Can you give more details if possible? What device, os version, etc?

We are soon adding other forms of signing up to address privacy concerns. Luckily, you dont have to sign up to use the site. Still, I hear you.

Thanks, Tom. I am still collecting feedback and trying to figure out the best solution for showing most value to users.

We recently launched Mobile Patterns - a comprehensive patterns gallery especially designed for the key players in the design community.

Designers at Mobile Patterns capture ‘WOW’ moments from commendable mobile apps and lead you to a vault of short videos of micro-interactions and user flows. It also has a top search bar that enables you to jump straight off to the interactions you desire to see.

We’d love to know what you think about Mobile Patterns and how we can shape ourselves into your personalised patterns gallery.

The phrase that Amazon used when launching lambda was 'deploy code not servers'. To me this sums up what 'serverless' means. It means the developer doesn't have to worry about servers in any way. With AWS Lambda/API Gateway (and arguably with Google App Engine before it) you take away the toil of having to:

  * Manage/deploy servers
  * Monitor/maintain/upgrade servers
  * Figuring out tools to deploy your app to your server
  * Scaling an app globally.
  * Coping with outages in a data-centre/availability
  * Worry about load-balancing & scaling infrastructure

I have actually thought about this idea before and really like what they are trying to do. But I do not like the idea of installing one more app and adopting one more platform.

Why not just use existing infrastructure of emails and integrate with that nicely? The channels on Twist could be folders on gmails (with google integration at first) and users could reply to threads from their favorite email client. If they want to use a dedicated app they could easily install the app.

I think this would help them with growth a lot more since it would use the existing infrastructure of emails. Of course, it doesn't solve the notifications problem that they are trying to solve but that's what the app is for.

I have actually thought about this idea before and really like what they are trying to do.

But I do not like the idea of installing one more app and adopting one more platform. Why not just use existing infrastructure of emails and integrate with that nicely?

The channels on Twist could be folders on gmails (with google integration at first) and users could reply to threads from their favorite email client. If they want to use a dedicated app they could easily install the app.

I think this would help them with growth a lot more since it would use the existing infrastructure of emails. Of course, it doesn't solve the notifications problem that they are trying to solve but that's what the app is for.

Exactly. Way to abandon most of older folks who actually purchase Skype credits.

PS. ux-app looks interesting. I can give some feed back as a designer if you want.

Really believe that Microsoft should have bought Slack. It makes perfect sense for them and aligns with their vision to be the productivity center of everyone's workflow.

Microsoft doesnt understand this space at all. Look what they are doing to Skype by making it more like Snapchat when their main use case is business related. Teams also feels so unfinished.