Did he say if he'd seen a working device, or confirm anything other than that it was him that appears on the KS page? Verifiable details from the creators are exceedingly thin on the ground. If you'd like to screencap your email and post a link to the image, that would be great. Thanks.

Wotao popped up (long ago) on the KS comments thread and basically said "I'm an investor but I can't really talk about anything". He also replied to direct emails to his uni email, confirming his involvement. One person who contacted him, reported him (not seen the email) as admitting he's not yet seen a working device.

I think he probably got pulled in as an investor (and to add credibility) and probably now rues the day he said yes. We'll see. Either way, at this point Google searches won't forget his involvement.

The thing also needs (most of its) power to run a Bluetooth receiver (+accelerometer), which typically uses 10-15ma @ 2V (=20-30mw) when in _receive_ mode. The duty cycle is short but waking up every 5 seconds to see if the tag is being pinged isn't typically something you'd power with leprechauns (unless they were made of lithium).

err... whose claims are unverifiable?

Wetag's? Sure, they're pretty sketchy. Practically no hard info except two wack pseudo-science documents and some nice photoshop work. No pics, no demo, no nothing (so far).

Mine? Errr... well, there's a ton of links to source material throughout, there's links to other people who think the same way (and did the math also), there's facts, figures, references, etc.
If you didn't click any of the links, do any Google searches, look at the iFind site or pay attention in math or physics class in highschool, then.. yes I suppose you find them unverifiable. Tell you what, I promise, cross my heart, it's all true. Does that work?

What you say is not plausible; how do you think any radio-activated device receives the "I lost you" signal? In practice it's far from "dormant 24/7"; it's completely deaf to any signal until it turns on its high gain radio which takes typically 10-15ma. The tag must be constantly waking up and consuming power (even if, as with BTLE, it's possible to set the gaps to e.g. 5-10seconds and the "on" time is very short).

Without trying to be unduly rude, you're 25% informed yet 75% confident in your knowledge, which I suspect comprises large portion of backers of this project.

Either do a little research (e.g. look up the math and/or read the datasheets for BTLE chips - all provided in the RTFA's google doc) or... go order a pack of 10 iFinds. . :-)

I did, see Google doc. So did others (better than me). Results posted in doc.

You say: "no idea, did not check it".

Your ideas are intriguing to me and I wish to subscribe to your newsletter.

It's not (just) for speed, if at all, it's BECAUSE YOU HAVE PORTABILITY WITH iOS (and other platforms)
If you use Java you're hosed. If you use regular C you can compile on both platforms, with a shim to interface to either iOS or Android as required.
The GLES code can easily be compatible. The UI stuff not so much but (high end) games generally implement their own UI in GL for specifically this reason.

It's not pretty but it's what most pro game developers have been doing since at least 2010, and it's a _hell_ of a lot better than having to totally rewrite your Java app in ObjectiveC or vice versa.

The extra performance is sometimes useful in some places but it's almost always about compatibility with iOS or (more rarely) with existing C libraries e.g. video encoding or whatever.

...in which case a Google Bus is going to appear out of nowhere and park between you and the moon, completely blocking your view.

You people are weird, I've been on 4x 1920x1200 monitors for years now (2x portrait, 2x landscape; It's fucking marvellous). I have a fifth but no desk space (or interest in turning head to view) so it's a spare.
This cost... I dunno, peanuts, even a few years back.
Super strongly recommend at _least_ a pair of portrait monitors plus at least one landscape. It's practically impossible to go back.

...you say that like that's a bad thing? This is Vegas!
Just make sure you have some potential customers with you and it's your card behind the bar (or in the stripper's hand, etc)

My scope HELL yes I use it! It's crappy - analog, 30Mhz(!!) and it cost about $60 on ebay but it's still very useful for all sorts of "WTF is going on". Wouldn't be without a scope for anything.

MUST-HAVE'S:
** Dual-output bench DC PSU (Instek) - can't BELIEVE I ever lived without one - what was I thinking? Ass-saving to have current display & esp current limiter(!) **

Logic Analyzer is an Intronix Logicport which does up to 500Mhz and has adjustable threshold voltage which is required for 3v3 / 1v2 designs; I have a Saleae16 but it's much less useful IMO; recommend to everyone to get a Logicport as well.

Fluke287 multimeter which is expensive for a multimeter but does microamp current measurements which you need for modern battery powered stuff (just don't blow the fu$e$ cos they ain't cheap)

Signal/protocol generator - I made my own! (a $12 Cypress FX2 board plus $6 AD9850 clock generator = output any protocol you can imagine on up to 16 channels @ 0-25Mhz with 0.001hz programmable clock resolution, super fucking handy)

Beagle USB protocol analyzer (although software-only ones are useful too)

Cheap chinese iron+hot-air combo (Kendal 852D) which is great

Love my FTDI quad-UART boards! - many things have multiple CPUs to keep track of nowadays. FTDI FTW. ..and whatever programmer/JTAG/etc the current CPU needs.

I find it very useful to run the logic analyzer and other USB tools on a separate PC & monitor to my "work" PC rig; makes them more like standalone tools.

...then they could use directional antennas on cell base-stations and divide up each cell into slices!!
Hey they could call them "sector antennas" and... oh never mind.

You picked Flex _and_ PHP as winners? Damn dude, don't ever go to Vegas.

Java? Casual? That's like saying the US Tax code is good bed-time reading.
After realizing I was spending half my frickin' life compiling, reloading, and waiting... waiting... (I'm looking at _you_ Tomcat) I switched to Python and never looked back.