Very cool project for those that only need protection locally with hand rolled rules. We're aiming to protect data flowing from SaaS solutions to LLMs and for those that don't want to manage the complexity of running a MITM locally.
Thank you for the feedback. There are about 230 rules currently available - with flexibility to add customize more as you see fit. Like you, my vision was, if I want to protect something I would not want to get it on wire in first place, hence local :)
We want to protect custom apps but also between all of the numerous SaaS products that don’t run locally and the guantlet of LLMs. We’re plug and play with virtually every SaaS offering that talks to LLMs.
and as I read more - it seems your solution is more aligned to specific industry vs I am approaching more from developer / general use perspective. cheers!
The biggest difference between the two apps is that BeerQuest is just as much about the place as it is about the beer. We don't rely on third party places data like Untappd does (Foursquare). Checkins are about checking into a place and not a beer. If you're at a place and are drinking a beer, you 'drink' a beer. We also think the journal and maps aspect of the app turned out really well. Quickly map out all of the great places near you and everywhere you been.
From a technical perspective, BeerQuest was built using Objective C instead of HTML5, so it feels like a true native app because it is.
I don't think so. The showcase on PhoneGap was posted in July 2012. Additionally, it's easy to tell that the app isn't utilizing the Cocoa Touch UI framework. Look at how the views bounce, how the buttons "feel". Those are dead PhoneGap giveaways.
I've found that most people don't care about this unless you're delivering an extraordinary native experience (ala Path)
A native app is great if you've got a team who can do it well. If you can't, simple PhoneGap-ish apps will suffice. It's a sunk cost in that if you get traction, you'll eventually need to switch over to native to compete: effectively a re-write.
Great feedback regarding the conversion rate. We actually went down the road of building both an iOS and an Android version out of the gate but found that the Android platform seemed fragmented. With hundreds of different devices all running everything from 2.x to 4.x, it seemed too complicated initially to do it right.
reply