Similar projects and alternatives to RVS_AutofillTextField based on common topics and language
Appwrite - The Open Source Firebase alternative introduces iOS support. Appwrite is an open source backend server that helps you build native iOS applications much faster with realtime APIs for authentication, databases, files storage, cloud functions and much more!
Static code analysis for 29 languages.. Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.
RVS_AutofillTextField reviews and mentions
Ask HN: How to get developers and UI designers to work well together
5 projects | news.ycombinator.com | 19 Jul 2022
I have had quite a bit of experience with this.
I'm primarily a native Apple application developer, but have done some backend stuff, as well. I have designed numerous Web sites, but I am not a particularly skilled Web designer.
I was, in the days of yore, an artist. I have also taken numerous design and usability course, from the likes of NNG (Nielsen-Norman Group).
I have designed a bunch of fancy widgets[0 - 4]. I actually use very few of them, because they are too intrusive.
I am in the "refining UX" stage of an iOS app that I've been developing for the last year and a half, or so. I'm working with designers and testers, to clean up the information architecture, interaction, usability, aesthetic design, and accessibility.
For me, the most valuable technique, has been rapid, high-quality prototyping. I have been abusing Apple's TestFlight beta release system, and have been using it to make regular (usually, a couple a day) releases to the rest of the team, who are mostly non-tech people. I've made over 600 releases. The first release was made less than a month after first code submission.
The way I use it, is that I run what I call "constant beta." The app is always at "ship" Quality, even if incomplete. This means that the code people get, is fully operational, for the currently developed feature set.
This has the advantage of constant vetting by Apple. They don't test TestFlight to the same level as the App Store, but they look for things like unsupported API usage, code signing issues, and obvious quality issues (like crashes). In at least one case, their testing found a crash that I missed.
Once the first release for a version has been vetted (takes a day or so), subsequent build releases, within that version are approved almost immediately, so I get quick turnaround.
If the testers encounter crashes, I get a fairly useless report. If I use a Ouija board, I can often figure out the general part of the application affected.
With this workflow, we can have a highly iterative process, with aesthetics, usability, and general UX, being tested, almost from the start.
I'm pretty good at interpreting designs. I can accept Figma, Photoshop, Sketch, Illustrator, Napkin Sketch, or Hand-Wavy Verbal Description, and turn it into UX. I usually have something for the designers to try out, within minutes.
Most of the actual code assets are generated via Illustrator, and I will often redesign raster art, into vector.
The designers and non-tech stakeholders seem to like it.
RiftValleySoftware/RVS_AutofillTextField is an open source project licensed under MIT License which is an OSI approved license.