News for hackers. Stuff that matters.
Re:Clinkle: App Teardown (Part 1) by volume on Saturday June 29, 2013 @10:22PM (#5964465)
1) I'm not familiar with intellectual property law and I'm curious: Can Clinkle's lawyers do anything to prevent such information from being published?

2) My inner conspiracy theorist says this is a clever posting from someone internal to Clinkle as a PR stunt.

Re:Clinkle: App Teardown (Part 1) by burgreblast on Saturday June 29, 2013 @11:09PM (#5964543)
3) Could someone nonplussed with the app, and wondering if hype was telling or misplaced. Seems reasonable to perform an iFixit style teardown, and see if there's any there there.
Re:Clinkle: App Teardown (Part 1) by 616c on Sunday June 30, 2013 @05:16AM (#5965197)
They could; Shazaam did something very similar.

https://news.ycombinator.com/item?id=5723863

Re:Clinkle: App Teardown (Part 1) by svstealth on Saturday June 29, 2013 @10:28PM (#5964473)
1) it was on the Google Play Store ... 'nuff said 2) why would they make fun of the stitched wallet leather look and the key used to unlock the wallet?
Re:Clinkle: App Teardown (Part 1) by huhtenberg on Sunday June 30, 2013 @05:22AM (#5965205)
> 2) a PR stunt

Came here to say just this. This looks very much like an astro-turfing post.

Re:Clinkle: App Teardown (Part 1) by 21echoes on Sunday June 30, 2013 @01:54PM (#5966530)
i don't think astroturfing posts are typically this negative..
Re:Clinkle: App Teardown (Part 1) by huhtenberg on Monday July 01, 2013 @10:11AM (#5970720)
It'd be a better way to astroturf actually. The goal of such post would be to merely put the company on a map and get people talking about it. Just set in a mood for now - it's something grand, mysterious and ambitious, if a bit half-baked (but that's just at the moment, that's why they are in "stealth" mode after all). The praise singing chorus will step in later.
Re:Clinkle: App Teardown (Part 1) by fblp on Saturday June 29, 2013 @11:19PM (#5964564)
Continued here: http://svstealth.tumblr.com/post/54200406550/clinkle-app-tea...

This part just mentions design, possible parter logos, fonts, facebook like boxes and that they didn't obfuscate code.

Re:Clinkle: App Teardown (Part 1) by pbreit on Sunday June 30, 2013 @01:39AM (#5964801)
Article seems unnecessarily mean.

A $25m "seed" is generally not a good idea but I think worthwhile giving the benefit of the doubt at this point and waiting to see what and how they roll out.

The Yodlee thing is likely for verifying bank/card accounts, not offering Mint-like services.

Re:Clinkle: App Teardown (Part 1) by icpmacdo on Saturday June 29, 2013 @08:43PM (#5964266)
With android apk's can so see the complete source code of the app?
Re:Clinkle: App Teardown (Part 1) by mbell on Saturday June 29, 2013 @08:48PM (#5964280)
Java class files (compiled Java) can be decompiled.

Unless they ran the code through an obfuscator or something in the android dev cycle does that automatically (I don't know), you can get the full source with full variable names, more or less. The stock javac compiler doesn't do much in terms of optimization, there are a couple things it does (replaces accesses to 'final static' members with constants for example), most is left to the JIT, bytecode -> source translation is pretty straight forward and you don't lose much.

Re:Clinkle: App Teardown (Part 1) by conradev on Saturday June 29, 2013 @08:47PM (#5964278)
No, but you can disassemble them to see the Dalvik bytecode[1], which is not too hard to understand.

[1] http://source.android.com/tech/dalvik/dalvik-bytecode.html

Re:Clinkle: App Teardown (Part 1) by wellboy on Saturday June 29, 2013 @08:49PM (#5964283)
You can actually reverse engineer an entire app to java code and see all the resources such as strings and images. Just takes around 10 minutes http://stackoverflow.com/questions/3593420/android-getting-s...

You can prevent this by obfuscating your code in eclipse with proguard, however most apps are not obfuscated.

Re:Clinkle: App Teardown (Part 1) by lnanek2 on Saturday June 29, 2013 @10:44PM (#5964502)
Even with obfuscation you tend to just end up with the code, but all the identifiers are replaced with a, b, c, etc.. I've still been able to figure Bluetooth protocols and other things without much trouble. For pirates, impersonators, and malware creators, they often just have to find free/pro/goods counter/license check/sig check or add in a call to their own extra code to run. So a little tougher for them, but not the end.
Re:Clinkle: App Teardown (Part 1) by maceip on Sunday June 30, 2013 @01:58AM (#5964840)
as mentioned, you can use a dalvik decompiler. I recommend JEB: http://www.android-decompiler.com/

It's like IDA but for APKs.

Re:Clinkle: App Teardown (Part 1) by gojomo on Sunday June 30, 2013 @02:32AM (#5964904)
Wow... blindly speculating yesterday about what Clinkle might be doing -- https://news.ycombinator.com/item?id=5956736 -- I'd thrown in "ultrasonic acoustics" as a random wild guess. Great to hear that's part of it.

Though it'd also be kind of cool to do the transaction in the hearable range... so your phone playing a merchant could make the same sort of 'honking' as old dial-up modems. Not just a novelty, that'd promote the service to everyone within earshot.

Re:Clinkle: App Teardown (Part 1) by bobo13579 on Sunday June 30, 2013 @01:22AM (#5964775)
This is a worse investment than color in my opinion. The founders have no track record whatsoever to justify a $25M investment for a product that has been stealth mode for two years running. I've heard several complaints from insiders about the company and its founder.