dansingerman

8 ms·

31.
by dansingerman 10y ago
Not convinced either way whether having the same interface for all of the stack is a good idea or not, but it did remind me of Joel Spolsky's blog post on leaky abstractions http://www.joelonsoftware.com/articles/L
32.
by dansingerman 10y ago
My take away from this is you need to ask 'why' as often as 'what' and 'how' when developing software. In my experience many software developers completely fail to challenge the 'why' of what they&#x2
33.
Are Apple selling harmful addictive substances to children?(blog.appapp.io)
2 points by dansingerman 10y ago|1 comments
34.
by dansingerman 10y ago
It's more then just that with heroku's random routing. If you are on shared tenancy dynos, and your current configuration is nearing maximum capacity, then adding dynos can reduce performance. Not per dyno, but across the entire p
35.
by dansingerman 10y ago
There's a very important metric they have left out of their data on settings for each test run: WEB_CONCURRENCY. While this will be different per app it will make a big difference to the performance. They mention they had 67 processes
36.
Introduction to an Event Tech Start Up(blog.evvnt.com)
1 points by dansingerman 10y ago|0 comments
37.
by dansingerman 10y ago
I've had great experiences with algolia. I've used it on numerous client projects, and my own product https://appapp.io . It is great as an out of the box search solution that will probably fit 90% of cases. It is blin
38.
by dansingerman 10y ago
Usually infomercial type blog posts like this turn me off both the content and the product, but this is a pretty great example of how to pimp your product through genuinely interesting content. I've rarely seen it done this well.
39.
The probability of human extinction(theatlantic.com)
5 points by dansingerman 10y ago|0 comments
40.
by dansingerman 11y ago
Shameless plug coming up: This is why I built https://appapp.io , so it would be possible to search for apps in the App Store (it's IOS only at the moment) while filtering out those with in-app purchases. I'd like to a
41.
by dansingerman 11y ago
Don't you think it is somewhat reductive not to even allude to that complexity in your article then? Without that, the article does seem to claim that just changing the label of the button had that effect.
42.
by dansingerman 11y ago
I just read the article for a second time. I am really not sure what assumption you think I am making is wrong?
43.
by dansingerman 11y ago
Yes, good software should abstract the complexity away from the customer. That does not mean the complexity does not exist. My post was motivated by the fact that the article is written as if this was a trivial change - "The designers
44.
by dansingerman 11y ago
It is way, way more than a day of work. That is my point. I expect it was measured in man-weeks.
45.
by dansingerman 11y ago
"All we did was change a button." I doubt it was that simple. The UX flow changes if you can purchase as a guest. More importantly, I expect when the system was built, the developers asked if all orders had a user, received the an
46.
by dansingerman 11y ago
Are you aware of imposter syndrome? https://en.wikipedia.org/wiki/Impostor_syndrome You may not be up to your job, but probably more likely it's that.
47.
by dansingerman 11y ago
Thanks. We have a lot of optimisation to do. When we launched we weren't sure to what extent we'd be indexed. Now that we know we are (by Google at least) we can put some focus on optimising our SERPS.
48.
by dansingerman 11y ago
Yes, we have more work to do to get Google to index all our content. It's still a bit of a mystery to us (Google webmaster tools tells us about 2500 pages are in their index) Our goal is not to have every app indexed (as that will by d
49.
by dansingerman 11y ago
We built our site, https://appapp.io (a search engine for the App Store) as a one page app. It serves no dynamic content in html from the server, so we were unsure to what extent google would spider/index it. As far as we c
50.
by dansingerman 11y ago
There's no mention of them trying to sell it. I wonder if they tried? I'd imagine anything with 1000s of paying customers would have some interest.
51.
by dansingerman 11y ago
It's Ember.js on the front end talking to an Algolia API. It's all proxied via CloudFlare, so very few requests hit our server (at Heroku)
52.
by dansingerman 11y ago
We can add that if you think it'd be a useful feature?
53.
by dansingerman 11y ago
As a starting point the site is part of the iTunes affiliate scheme. Hosting costs are fairly small, so as long as it covers its costs it'll be live perpetually. We also have other ideas for sources of revenue, this is just the MVP.
54.
by dansingerman 11y ago
That's a great idea.
55.
by dansingerman 11y ago
Good idea!
56.
by dansingerman 11y ago
I totally agree. Finding out which apps have ads like that is non-trivial, but we'll certainly look into it.
57.
by dansingerman 11y ago
fnd.io talks directly to Apple's search API (which is one of our sources). What fnd.io does not let you do is filter results by all the criteria we provide (we consider that our main USP). e.g you can't find pay once games on fnd.
58.
by dansingerman 11y ago
There's a number of sources that need to be stitched together. The official Apple sources are - iTunes search API: https://www.apple.com/itunes/affiliates/resources/documentat... - Apple's Enterpris
59.
by dansingerman 11y ago
I suspect what you are seeing are the titles - but the nature of Apple's search encourages App developers to stuff their titles with keywords.
60.
by dansingerman 11y ago
Formally, no. I have had it beta tested by friends and family, and that is not something that has been mentioned. I do have sympathy with your view on the desktop version. It originates from the mobile version (which was written first) whic

More ›