Hacker News new | comments | ask | show | jobs | submit login

I'm struck that it appears to do very little local caching. In that sense it feels like a highly polished web app, always at the mercy of an available network.

Also, it's iPhone-only. Following the direct download link from an iPod or iPad yields an error. Guess I'm sticking with Boxcar for iPad push notifications.

Guess I'm sticking with Boxcar for iPad push notifications.

Same here, except using Notifo.

The inbox is incredibly slow to load up ("refreshing conversations...") compared to the native SMS app or even Whatsapp (iPhone 4, 4.2, 3G 3 bars). And while it loads up, it doesn't seem to be possible to switch from the inbox to the dialer or the "Menu"... It's also crashed twice when opening after receiving a text notification. (disappointed sigh).

The "no caching" effect is much less pronounced with fast app switching. Are you on iOS 3.x?

Also, in my experience, there are often weird consistency errors in the App Store when something new is rolling out. (I could only see it on my Mac for a while before it appeared on my phone.) Try again in an hour.

I'm on 4.1. I noticed the caching behavior after seeing that the text and voicemail views start with no data loaded, even after viewing the inbox. Forcing the app to exit zeroed out all three views.

Loading data is pretty fast on wifi, and the app is certainly nice to look at, but not taking any advantage of local persistence seems to push the web-centric worldview a step too far.

Thanks for staying around. We have some really cool stuff coming up @Boxcar.

Applications are open for YC Summer 2019

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact