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.
We're using a proprietary multi-layered algorithm that combines a series of criteria, checks, and heuristics to assess each email address.
It includes:
Format and domain-level validations
SMTP-level interaction with fallback logic
Detection of disposable domains, catch-all behavior, and risky patterns
A scoring model that returns both a risk label (valid, risky, invalid) and a confidence score (0.0 to 1.0)
And much more — especially for nuanced edge cases and deliverability signals
Unlike many validators that return a binary result, MailShrimp gives you both a label and a score, so you can decide what’s safe to keep based on your own thresholds.
We're also focused on speed and usability.
Our logic is designed to handle edge cases often missed by more generic tools.
Yes, we’ve tried Emailable — solid tool, but quite expensive in the long run.
MailShrimp is built to be much more lightweight, transparent, and affordable (starts at $14.90/month for 10,000 validations) — and you can try it for free.
Would love to hear your thoughts if you give it a spin.
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
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
Thank you! I do see the use for these, though a few things are a little off target for what the app hopes to solve. Component preview and mock props is actually something I have planned for the future with a subtype of snippet for templates, so when you intend to have custom inputs there is a way to test with different data. First though I'd have to build a different system for live previews and a dynamic environment that can adapt to which component it might be hosting.
Storing in the cloud to grab them with something like a cli tool is super cool. I have a feature on the mvp+ list to download a list as a library or to fork to github as a lib, just converting it into a folder. But I'm trying not to let scope creep distract me from just making it as easy as possible to grab a quick tool without downloading a whole library, not trying to compete with npm or any other package/version manager.
At present the only AI features I can think could benefit the app are search tools and framework detection, but these can also be improved traditionally without the need for linear algebra or paying for use of any ai api I think.
Basic version control could be cool too! like storing previous versions if a tool was useful to you in different forms
I do overall though feel the goal of this is a little different from the Bit platform, but some lessons could be learned about what people want based on the product's popularity :)
It has most of the things you said: Create your own component library, easily share through cloud, import and use them, live view and edit them online at Studio [1]
I'm also working on adding versioning and a NPM package so you can refer to your components with unique IDs and directly use them in your code.
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?
Yes, the main idea is to clone existing components and to modify them for your own website (use-case) design. You can also create from scratch using the Studio. In both cases you can save and host the components in the cloud.
(Evil laugh). YC could fund it so that it becomes the best AI to do this. Since they know who used it, they are immune from being bamboozled by it’s funding applications while other VCs now need to deal with mountains of spam.
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!
