@BrandonButch
I watched your video about using Apple Calendar, and being an active calendar user as well, I thought you would appreciate event management and sharing tool. Don't sleep on batch events!
Let me know what you think https://t.co/BP7jydyIQA
@IvanMartinac Yeah exactly, false positives or negatives would be the best but those are a bit hard to stumble across and time consuming as well. Next best thing would be new rule suggestions which I could incorporate in next version, and general UX feedback would be great.
@IvanMartinac For now it does static code analysis and based on results it suggests to cover missing accessibility labels, dynamic size compliance and few other rules incorporated in this version. You can point it to your source code and if you worry about privacy, it's all run locally
Building this solo and shipping in public.
Question for iOS devs: what's the accessibility mistake you catch yourself making the most? I want to turn the top answers into rules.
Drop it below 👇 and I'll reply to each one.
The EU Accessibility Act is now law.
If your iOS app ships in Europe and isn't accessible, that's a legal problem, not a "nice to have."
So I spent the last few weeks building a macOS app that catches accessibility bugs before they ship.
Here's what I learned:
What surprised me most:
The 12 fake-broken files were 10x harder to get right than the 7 actually-broken ones.
Building software that knows when to stay quiet is way harder than building software that talks.
hey Artem thanks for diving into this topic. I mainly wanted to push 2 flows:
1. accumulate batch of events and import them to own calendar;
2. generate event(s) and share via QR code. (both flows can import to own code and share via QR, this was just the idea)
with that in mind, I was going to target personal schedules more than teams, as teams probably already have some kind of event sync tool. This would be more of a sync tool for your group chats