Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
nfarina
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
Providing Indoor Location in the Real World
(nfarina.com)
12 points
by
nfarina
11y ago
|
0 comments
2.
▲
by
nfarina
12y ago
Scanning for arbitrary beacon IDs is not possible on iOS by Apple's design. You could certainly do that on Android however.
3.
▲
by
nfarina
12y ago
Absolutely true, but this is also possible with just about every other technology today. "Bad Apps" can report information about Beacons, GPS, or any other sensor on the phone they have access to.
4.
▲
by
nfarina
12y ago
I think the technology here is so deceptively simple and generic that it's hard to say what the true killer use case is yet. It's definitely unfortunate that the "ads" examples are the most prevalent. Despite that, I
5.
▲
by
nfarina
12y ago
These kind of experiences are entirely up to the app developer to implement properly in a way that's not annoying like you describe. It can be done in a way that is nice (i.e. not notifying over and over). Not saying they'll all d
6.
▲
by
nfarina
12y ago
I think everyone's trying to save retailers from Amazon :)
7.
▲
by
nfarina
12y ago
It's a tradeoff. Packing more data into the beacon would mean more spectrum used per beacon - also, changing what the beacons are saying is much harder than flipping a switch on a cloud server. Also it's not required that you go t
8.
▲
by
nfarina
12y ago
For region monitoring (typically used for the "notification" case) the limit of "fences" is indeed 20...it gets into a bit more detail about "what's a fence" [edit: most of the time you can assume one moni
9.
▲
by
nfarina
12y ago
It was surprisingly challenging to come up with just those two examples to be honest. I don't think we really know what the killer location-based notifications are going to be yet.
10.
▲
by
nfarina
12y ago
Wifi-Beacon interop is quite new; it turns out the Wifi network at Levi's is really dense so it does have insane coverage. Also the Beacons are surprisingly visible even without further interop tricks - you can see them across the st
11.
▲
by
nfarina
12y ago
Absolutely ... this wasn't an entirely new "invention," although Apple's technique of cramming their metadata in the spec is definitely novel, although nonstandard.
12.
▲
Let's Talk About Beacons
(nfarina.com)
219 points
by
nfarina
12y ago
|
93 comments
13.
▲
Freeing "Feeds": From Paid App to Open Source
(nfarina.com)
1 points
by
nfarina
13y ago
|
0 comments
14.
▲
by
nfarina
14y ago
I think the general source of frustration with Sparrow's acquisition is the feeling that something beautiful just got end-of-lifed. And of course that this is just the latest in a line of could-have-beens like PushPopPress, Tweetie, etc. An
15.
▲
by
nfarina
14y ago
Amazing! It worked perfectly on my iPad and I was able to figure it out quite naturally. Really impressive for a "demo project."
16.
▲
Windows Mobile: Before Location was Cool
(nfarina.com)
7 points
by
nfarina
15y ago
|
0 comments
17.
▲
by
nfarina
15y ago
This. His writing was life-changing for me in many ways. Incredibly accessible, useful discussion of various human logic fallacies. Fundamental misattribution error FTW!
18.
▲
by
nfarina
15y ago
Ah ha, yes, you are correct - but packfiles combine multiple blobs together to benefit from additional compression that you couldn't achieve by compressing each individually.
19.
▲
by
nfarina
15y ago
Git actually starts compacting your object database and creating super-efficient delta-compressed packfiles after a bit. You can still throw object files in there afterwards though, and it doesn't change the basic principles of operation.
20.
▲
by
nfarina
15y ago
Part of it was that SVN was the last service running on a server I wanted to shut down. The other part was simply momentum. Github (and therefore Git) were too exciting to not want to be a part of. I didn't want to be left behind. That said
21.
▲
by
nfarina
15y ago
I wish I had written your first line!
22.
▲
Git Is Simpler Than You Think
(nfarina.com)
609 points
by
nfarina
15y ago
|
118 comments
23.
▲
by
nfarina
15y ago
My sarcasm may have been too subtle there; I definitely think it's a bummer that you have to own a Mac to develop for iOS.
24.
▲
by
nfarina
15y ago
Just increased the quota. Humbling.
25.
▲
by
nfarina
15y ago
The OpenGL-nature of iOS was explained to me at WWDC by the head of graphics at Apple. But you can never be sure of anything!
26.
▲
by
nfarina
15y ago
I thought the Android docs were quite good for the most part, but I usually just Google my questions and end up on StackOverflow. I'd love to give StackOverflow a great big hug someday.
27.
▲
by
nfarina
15y ago
I "learned" Java in college, but didn't use it after graduating in '02. I was quite pleasantly surprised by all the (new to me) stuff like "anonymous inner classes," and ultimately I've come to respect the staunch minimalism of the language
28.
▲
An iOS Developer Takes on Android
(nfarina.com)
720 points
by
nfarina
15y ago
|
116 comments
29.
▲
by
nfarina
15y ago
Totally agree. His begrudging "It's ok, I guess" conclusion doesn't make the rest of it any more insightful. It's all the worst sort of locker-room gossip.
30.
▲
by
nfarina
15y ago
Completely agree. Cocoa is appropriate for creating minimalist, system-styled UI. Not for rich flow-based content rendering. See Versions.app: native where it makes sense (filesystem treeview), Webkit elsewhere (history browser).
More ›