HNHacker News
TopNewBestAskShowJobs

Guzba

1,178 karma · joined August 28, 2010

Cofounder, https://www.pushbullet.com W14 --- ryan@guzba.com
submissionscomments
Guzba··on Real-time notification mirroring from Android to your computer
We have a plan for earning revenue but haven't deployed it yet. This feature furthers our vision for notifications as does the rest of our service. We'll be focusing on revenue soon but right now we're focused on growing since people are excited to sign up.
Guzba··on Real-time notification mirroring from Android to your computer
(Dev here) You've got the basic idea. We do everything over https of course, but you are still sending your data through our servers.
Guzba··on Relying on a Google API and going over the quota on launch day
This is great. I totally did that on purpose (lining it up vertically and everything) but I figured I'd never hear anyone comment on it :)
Guzba··on Relying on a Google API and going over the quota on launch day
Using GCM for Chrome is free but you do have to have an API key (unlike some Google services). The 10,000 messages cap is is what they call a courtesy limit, hinting that you can get it increased, but we had never gone through the process of requesting one, nor did we feel we were necessarily guaranteed an increase.

(Adding a credit card didn't let us increase the cap.)

Guzba··on Building a TCP API: How we built our realtime app, Filmgrain, part 2
This is all true, and HTTP really is a great choice, but that's the point I'm trying to make--it's a choice and there are alternatives. Specifically for mobile apps, those alternative are really attractive.
Guzba··on Building a TCP API: How we built our realtime app, Filmgrain, part 2
Websockets are the natural choice when/if we bring Filmgrain to the browser. I actually think Websockets are really exciting, but for a mobile app just going straight socket made more sense.
Guzba··on Building a TCP API: How we built our realtime app, Filmgrain, part 2
Web sockets are great for getting TCP in the browser but since we're only building mobile apps right now, we don't need the HTTP layer, instead we're using straight sockets.
Guzba··on How we built our realtime app, Filmgrain, part 1 - the backend
Right now we don't have user accounts or anything mission critical to store. (Everything we use Redis for right now is essentially app state and we use it to managing cross-machine communications.)

When we have user accounts and other things like that, we'll have to think about how to do that the most reliable way as well, which may be Redis or may mean bringing Postgres into the mix. I think there's a lot of benefits to keeping the variety of technologies down so if we were to bring in another, it would need to offer something compelling that our current mix doesn't offer.

The major theme we were trying to highlight in this post is just how far Redis can take you if you're trying to build a component-based backend and need a way to handle the communication as well as the state of the system.

Guzba··on How we built our realtime app, Filmgrain, part 1 - the backend
Why do you think that?
Guzba··on How we built our realtime app, Filmgrain, part 1 - the backend
When we started working on Filmgrain, what became clear was that it wasn't so much that the popularity told you if the movie was good or bad, it was that it worked remarkably well at highlighting the movies people care about right now. I know many of us watch critic reviews to see if a movie is any good before going, but I don't think this is the norm. Many people just get excited about a movie and then go see it.

The other cool thing that Filmgrain captures that's different from quality is insight into what people liked about a movie afterwords. For example, people were divided on if Great Gatsby was good or not, but people couldn't stop tweeting about the soundtrack. I'd have never known how much people cared if it wasn't for this feed and it's this type of meta information we want to bring forward, as we can.

Guzba··on Show HN: Filmgrain, a realtime movie + Twitter app
Thanks a lot. Also, it's definitely possible an iOS app is already in the works :)
Guzba··on Show HN: Filmgrain, a realtime movie + Twitter app
I actually built this with two friends and our goal was to build something together and play with realtime in an app. As far as our plans, getting this far feels great and we're excited to see how people feel about the app. If people like it even a little, I know we'll keep going.
Guzba··on Show HN: Filmgrain, a realtime movie + Twitter app
Here's the launch blog post, too, if you're so incline. http://blog.filmgrainapp.com/2013/06/15/filmgrain-is-live/
Guzba··on Hello, PushBullet - push anything to your Android phone from your browser
No, its not. I just haven't had the time to get that far. It's a hard problem but selling emails isn't an option.
Guzba··on PushBullet: From 0 to 15,000 users in 2 weeks
I have hey@pushbullet.com on the Play Store for feedback, and yeah I should get a contact page up on the website too.
Guzba··on PushBullet: From 0 to 15,000 users in 2 weeks
There might have been, it wouldn't surprise me if they were talking about Chrome to Phone, an extension for Chrome they built for pushing to your Android phone.

The problem is Google never really took it any further and stopped supporting it. Classic example of a project that simply withered without any love.

Guzba··on PushBullet: From 0 to 15,000 users in 2 weeks
Eventually, of course. Right now though I have a ton on my plate as it is and zero iPhone experience :)
Guzba··on PushBullet: From 0 to 15,000 users in 2 weeks
Glad you like the app! And the Chrome extension will pre-fill for the page you're on, but not for tabs you had open before you installed the extension :)
Guzba··on PushBullet: From 0 to 15,000 users in 2 weeks
I agree with your assessment that active users is the only count that really matters. I haven't actually got the numbers myself but I watch the split between users and things pushed and it is growing wider every day. This is my proxy right now.

I haven't messed with weekly active users, for example, because my sample space of time is so small I couldn't really make any statements.

The other thing I take as a good sign is that the number of registered devices has officially overtaken the number of registered users, meaning people have taken the time to register more than one device more often than not even registering one.

Guzba··on PushBullet: From 0 to 15,000 users in 2 weeks
Other than paying for the 'infrastructure', which isn't much yet, I haven't had to spend any money on user acquisition.
Guzba··on PushBullet: From 0 to 15,000 users in 2 weeks
Actually, I'm using Google's Cloud Messaging infrastructure which means I get the benefit of the same technology Google uses to deliver Gmail notifications, etc. It also means there isn't any incremental battery life harm. :)
Guzba··on PushBullet: From 0 to 15,000 users in 2 weeks
I'm basically just using it as memached right now. I need to use something since I have more than one app server so storing it in memory on the machines won't work.
Guzba··on PushBullet: From 0 to 15,000 users in 2 weeks
Basically, its a superset of Chrome-to-Phone functionality that supports newer devices and takes advantage of the new notification features in Jelly Bean. Hope that helps :)
Guzba··on PushBullet: From 0 to 15,000 users in 2 weeks
Ah, thanks for pointing this out. I'll push the fix as soon as all of this dies down. No need to rock the boat while there's a party :)
Guzba··on PushBullet: From 0 to 15,000 users in 2 weeks
I really liked this post so I'll share a funny story about the Chrome extension.

I spent a couple evenings getting pseudo-authentication working with OAuth to log people into the extension, it was annoying and a real pain.

Then, the third evening, I realized that as an extension, any ajax request I make will have access to the same pool of cookies as normal browser requests, so it turned out that if a user is logged in on the site, they're automatically logged in on the extension, too.

This made everything SO much easier, but I had wasted like 8 hours of work to get there :)

Guzba··on PushBullet: From 0 to 15,000 users in 2 weeks
I actually submitted the launch post on reddit as an afterthought to the HN submission and was shocked when it was going better than the HN post. It kind of destroyed my preconceived notions of HN as the best launchpad and reddit as no-op on that front.

I had a couple friends I told about it and I'm sure they upvoted the submission, but I think really I did well because PushBullet is exciting to Android users and r/android is a hotbed of people looking for exciting things to do with the devices they know have a ton of potential.

Guzba··on PushBullet: From 0 to 15,000 users in 2 weeks
Presently no, thats something I need to get on.

I've set up an account and am leaning toward SendGrid right now since I dont need an SMTP server as MailGun requires.

Am I wrong about that, btw? It's all new to me. (I use Google Apps for Gmail, etc. and MailGun wants the email dns stuff which is a problem.)

Guzba··on PushBullet: From 0 to 15,000 users in 2 weeks
Presently, $0. Yeah, I know that's not as good as anything > $0 but two weeks ago I didn't think this was going to be a 'real thing'.

I'll figure something out, I work full time so I can manage the costs without noticing but that isn't an answer so much as a deflection :)

Guzba··on PushBullet: From 0 to 15,000 users in 2 weeks
Files are pass-through uploaded from users to an S3 bucket and given a UUID name. That name is stored with the push data in Postgres and a GCM tickle is sent to their phone with a push_id to act on.

The app receives the tickle and makes a quick api call for the push data and sees it needs to get a file. It then asks for the file and I make sure they have permission to download it and then let them.

Over engineered? Maybe :)

Guzba··on Hello, PushBullet - push anything to your Android phone from your browser
Good question. I use Google's Cloud Messaging to actually deliver the pushes but the data in a push is not plaintext, and the push sometimes doesn't even have the data at all (the GCM message is just a tickle). All interaction with PushBullet app servers is done by https. Overall, I don't think I've done anything stupid but I wouldn't trust PushBullet to anything you consider prudently private.
← PreviousPage 4 of 5Next →