Please… Enough with the Sloppy, One-Shot SaaS Replacements — Mahmoud Abdelwahab, Railway

Key takeaways

1. Structured Codebase is Key 3:30

   When building tools for daily use, providing the agent with a proper codebase containing solid abstractions ensures that new features follow existing patterns, leading to a more consistent and polished result.

2. Implement Autosave and Collaboration 7:37

   For document editors, autosave should be a non-blocking background action. Advanced features include preventing tab closure on unsaved changes and enabling real-time collaboration.

3. Use Optimistic Updates 9:20

   Instead of showing loading spinners for every action, optimistically show the success state immediately. If the background sync fails, the system should roll back the change, making the overall experience feel significantly faster and snappier.

4. Enhance User Control (Undo/Archive) 10:16

   Improve UX by allowing users to undo actions (e.g., deleting a record) by immediately removing the item from the UI but keeping it available for a short period. Use archiving instead of forced deletion to hide records from the UI or search results.

5. Manage State with URL State and Infinite Scroll

   Persisting filtered or sorted views in the URL state makes the view shareable. Additionally, implementing infinite scrolling removes repetitive navigation by fetching data as the user scrolls, rather than requiring 'Load More' clicks.

6. Package Preferences as Agent Skills

   To enforce consistency, package recurring design and deployment preferences (e.g., UI/UX standards, animations, platform-specific integrations like Railway) into explicit 'agent skills' for the AI to follow.

7. Mandate End-to-End Verification

   The final, crucial step is implementing a verification loop. The agent must not only report that the build and tests passed but must also run the feature end-to-end to ensure a fully functional and polished experience.