Nice. Obviously this is a huge issue many are trying to solve. Providing agents with a keychain is one thing, but how does this solve the issue of using these keys in projects? Does the agent decrypt it and set it in a .env? Is the CLI required to be used in the build process?
If you can submit a screenshot or crash report via test flight that would help. There’s also a Debug option in settings. It lets you email those logs to me, which would be helpful
Right now I’m doing it simply by inserting history into a DB and calculating it just by the amount of times in the last 60 days. I plan to do more complex statistics later on, I think there’s more to do there.
I was pleasantly surprised with how both Codex and Claude helped me with this. I’ve been meaning to learn ios dev for the longest time and I’m really glad I finally managed to give it a try while having enough help doing it! I’m a React developer for the most part.
I’ve been building an iOS app called ViaNJ, an unofficial real-time NJ Transit companion. It’s my first iOS project and I’ve been enjoying playing around with Xcode (and various AIs to help out).
It shows live departures and mobile ticket integration with Apple Wallet passes, track predictions, with plans for alerts, GPS-based train map, Live Activities… and more.
I’d love help from the community testing it, finding bugs, and suggesting improvements. It’s been a fun side project, and I’m looking for feedback on what features matter most to daily commuters.
Maybe they changed their pricing but my team paid $25 for 25,000 validations as a one time thing. We’re not in need of 10,000 a month so I wouldn’t be able to try it out soon. But yeah I guess I’m just still not sure how it’s that different from Emailable. Not that there’s any issue with competition of course!
Since I could not find any examples of this online, and had to figure it out, I wanted to share it online.
This React TypeScript project demonstrates a Braintree OAuth integration flow between two merchants. It showcases how Merchant A can obtain authorization from Merchant B to perform actions on their behalf using Braintree's OAuth and transaction APIs.
In this example, Merchant A provides this application to Merchant B, allowing them to:
Grant OAuth permissions to Merchant A
Allow access to customer payment methods
Enable facilitated transactions
The integration uses two main Braintree APIs:
Access Token API - For OAuth authentication
Transaction API - For creating Shared Vault Transactions
Confused, this looks more like a tool that pulls existing HTML from other websites. Is the idea to create your component library by cloning existing components that are out there and modifying them? And then they are hosted in this cloud library of sorts?
This actually has a lot of potential I think. It reminds me of https://bit.dev (obviously without most of the main features). But the core is there - the idea that components should be organized in a way that makes them easily reusable.
If you were to add a preview functionality of each component, this would already look A LOT like the Bit platform.
Personally, I've been trying to figure out a way to create a component library where my components are easily shareable and importable, but haven't yet come to a real solution. Bit is a good one but I am not yet ready to pay per component after my 20 free components are used up.
I think this would be actually extremely useful to me personally if you added these two things:
- component live preview (perhaps with mock props/data?)
- a way to store the components in the cloud so that they can be important into any project, where the source of truth is in this cloud platform
Ever hear about Levels by Derrick Reimer? Seems like this is trying to accomplish the same thing. He eventually shut it down though. Looks like you got YC funding though so that’s huge!