HN user

ananddass

982 karma
Posts33
Comments86
View on HN
medium.com 10y ago

The Power of Core Values

ananddass
6pts0
medium.com 10y ago

Mastering Coffee Delivery, One Tray at a Time

ananddass
47pts11
infowetrust.com 12y ago

Government shutdown: a brief history

ananddass
1pts0
daslee.me 12y ago

Photo-sharing Fatigue

ananddass
2pts1
blog.inkmobility.com 12y ago

What’s Missing in Android Intents

ananddass
12pts6
blog.inkmobility.com 12y ago

What iOS Can Learn from Unix

ananddass
52pts58
blog.inkmobility.com 12y ago

Experiment: To work primarily on an iPad for a week

ananddass
52pts59
blog.inkmobility.com 12y ago

IOS productivity app market on the cusp of change?

ananddass
43pts45
blog.zencoder.com 13y ago

Zencoder and Filepicker.io — Look ma, no backend uploading and encoding

ananddass
9pts0
blog.programmableweb.com 13y ago

Handling Errors in Javascript APIs

ananddass
19pts1
blog.filepicker.io 13y ago

Do name-your-price models yield revenue?

ananddass
13pts12
blog.filepicker.io 13y ago

The “Few Months In” Checkup for Startups

ananddass
100pts20
www.milouchev.com 13y ago

Found a bug in Gmail, Cloudy fixes it

ananddass
7pts2
blog.filepicker.io 13y ago

How to sell to large customers

ananddass
68pts27
blog.filepicker.io 13y ago

Designing Javascript APIs

ananddass
71pts10
blog.filepicker.io 13y ago

Security on an untrusted client - locking down a javascript library

ananddass
31pts22
blog.filepicker.io 13y ago

Chrome extension - Attach files from the cloud to Gmail using Filepicker.io

ananddass
35pts2
blog.filepicker.io 13y ago

When you learn your customers aren’t just API calls

ananddass
15pts5
blog.filepicker.io 13y ago

HTML5 apps: Silk, Audiograph, Circuitlab

ananddass
49pts6
blog.filepicker.io 13y ago

Keep your tools sharp

ananddass
12pts2
www.filepicker.io 13y ago

Filepicker.io launches Alfresco, WebDAV, & FTP integrations

ananddass
40pts12
blog.filepicker.io 13y ago

How to hire a sales person

ananddass
55pts29
blog.filepicker.io 13y ago

Hacks from PennApps, largest student-run hackathon

ananddass
23pts15
blog.filepicker.io 13y ago

Photo uploading is broken

ananddass
61pts36
dchang.mit.edu 13y ago

Show HN: Choose Photo. Make Ascii

ananddass
116pts32
plus.google.com 13y ago

Scoble: Filepicker.io helps you offer great cloud-handling features

ananddass
14pts6
www.fabrizio-branca.de 13y ago

Show HN: Open-source content management system:TYPO3 and filepicker integration

ananddass
12pts0
www.fabrizio-branca.de 14y ago

Easily upload eCommerce images

ananddass
7pts1
blog.filepicker.io 14y ago

HN Prefers Vi over Emacs

ananddass
16pts4
blog.filepicker.io 14y ago

Common problems with large file uploads

ananddass
72pts34

Disclosure: I am on the B.D & partnerships team on Postmates.

We haven't shifted focus away from restaurants. We have about 3000 Plus partners today of which a majority are restaurants. We've always done more than restaurants. Food is most of what we do but there are also grocery, apparel, electronics, essentials retailers on Postmates.

It really depends on the order distribution of distances for a specific store but on average its ~7 minutes from pickup to dropoff. Regarding difference in temperature, the coffee travels in insulated bags and so we aren't seeing significant differences. We are monitoring customer satisfaction scores on these orders and will tweak as we go along as we find opportunities.

Actually, Postmates & Starbucks have been working on this partnership for a while now. We began operationally testing this in the last couple of months. As with all tests, there were kinks that needed to be worked out and new problems to be solved. Transporting coffee, spill-proof, at scale was one of those.

It is true that app quality has a lot to do with the experiment. I was surprised by how many of the problems could be solved if the apps upped their game. Hardware limitations were secondary only to the software experience.

So one of the things interviewees mentioned is that there was a difference between "micro moments" and "full blown work".

Writing a paper is full blown work that they know they cant do on a mobile device. But they expected a lot of the micro-moments to work.

Curious as to why would engagement and retention be low? As regard's pay per download models...looks like "Attach" business model's are becoming more popular.

"Attach" means charging for something outside of the app store. Dropbox, Uber, Square all do it. I remember seeing a Chris Dixon post about this on HN a few months ago.

Sorry, I should have added more references in that connected the dots better. A lot of capital and talent is flowing into solving the problem. Thus, we are likely to see some big shifts. --$4 billion invested into "business/office" software on iOS since 2010 http://readwrite.com/2013/06/25/a-new-golden-age-of-producti... --Mailbox's exit to Dropbox --Quip openly calling for a change to the word processor https://quip.com/blog/introducing-quip

Yes. The keyboard problem is a big one. It was so painful that I had to buy a bluetooth keyboard just to work with my iPad. That's a hard one to solve until apple comes up with something better user input device. (e.g. thalmic labs, leap motion etc).

After I bought my keyboard, the next problem I hit was the inter-app communication issue you raised. That's a software problem and solvable.

Fair point Chris. User testing has been changed to usability testing throughout the article. Referenced your comment on HN

Unfortunately, I couldn’t change the title as it would break the url which has been reblogged and distributed.

It makes sense to pass files by reference rather than by value. This integration example would allow you to send files as urls via the SMS protocol instead of sending blobs of data.

Mobile network bandwidth is certainly a constraint in the US (cellular networks throttling high data usage subs is a proof of that). Viewed in that context pass by reference makes greater sense.

Jordan and team are good friends of ours (Filepicker.io team). We are trying to solve similar problems but approaching it from different directions. Its going to be an interesting future. :-)

Groxx you make a great point. We had the donate button only in the registration page when the API key was generated. Not in the documentation page not did we do a time lapsed reminder. May be the outcome would have been different.

Should have articulated this better in the original post [I am not a lawyer so I'd suggest talking to yours to nail it down.]

1. 1099-k: over $20,000 in goods and services sales and completed 200 transactions.

There is an Etsy link quoted in the comments that explains Paypal's role in these transactions clearly.

2. 1099-MISC forms: Paypal used to issue 1099-MISC. They stopped issuing these since they discontinued the option to direct debit your money market account for payments.

Hope this clarifies.

[Edit]-just got off the phone with Paypal support and they confirmed that they don't issue 1099-Misc

[Edit-2]-proof why things like this are a time sink! outsource and get back to building product and talking to users.

Having Reddit do it themselves may increase the authenticity of the recommendations. Also you might want to look into subreddits like Redditgifts. As noted before, there is a lot of valuable data hidden in those conversations.

We intentionally chose to focus on making the integration as easy as possible. The key is to get the customer to try a proof of concept as easily as possible. We still need to do a better job of it.

hmmm it seems like the key is to find the balance between evangelizing your product/vision while genuinely soliciting inputs from the C level on what their priorities are. Hopefully there will be a match somewhere in that conversation

Agree. It needs a deft touch. From a social engineering standpoint you have to build sponsorship with X and have him suggest who else to meet.

I'll keep the response specific to sales objections that a growth stage startups face

Scalability objections: can you scale to our volumes? Respond with suggestions for a phased roll out. Take your backend expert in to the meeting and present credibility on why you can scale.

Company objections: will you be around for long? What if you get aquihired?

Reiterate vision behind why are doing your startup (hopefully the right reasons). Talk about your investors and the expectations/commitments made.

Control objections: "We are uncomfortable giving up control over this part of our tech stack"

Try to create analogies. Understand other parts of the stack that they have given up control over and why they feel comfortable with those. Feed those expectations back as contractual commitments that you are comfortable making.