Major UI Update: Item Name Field + Improved Line Item Structure + Global Currency Support
Hi Indie Hackers đź‘‹
Just pushed a set of meaningful improvements to invoice.gen.in based on early feedback and real usage patterns.
### ✅ New: Dedicated “Item Name” Field
Previously, line items only had a description field.
Now each line item has:
• Item Name (primary field)
• Expandable Description (optional)
• Photo attachment (optional)
This makes invoices more structured and professional while keeping the interface clean.
The description field is now hidden behind a toggle to reduce clutter and maintain simplicity for users who don’t need extra detail.
---
### 🌍 Global Currency Support
You can now generate invoices in multiple currencies — helpful for freelancers and service professionals working with international clients.
---
### 🧾 Improved Template Selection
Added clearer template modes:
• Classic Pro (inline photos + attachments)
• Inline Photo (photos within line items)
• Attachment-Only (proof section separated)
This gives flexibility without overwhelming users with complexity.
---
### What I’m Observing
The strongest resonance so far seems to be with contractors and field service professionals where proof-of-work reduces disputes and approval friction.
Currently focused on:
• Usability refinements
• Observing repeat usage patterns
• Sharpening positioning based on retention
Appreciate all the feedback so far — it directly shaped these improvements.
Nice iteration. The structured item name plus optional description keeps the UI clean while increasing professionalism. The template clarity is also strong. It feels intentional, not bloated.
Since you’re handling invoices, attachments, and proof-of-work photos, a few security questions come to mind:
• How are you isolating user data at the database level to prevent cross-account access?
• If invoices are shareable via public links, are those links protected against enumeration?
• Can users export and permanently delete their full invoice history?
Invoices contain names, addresses, payment details, sometimes tax IDs. That’s sensitive business data.
We’re the Nautillo Pro security team, so we naturally look at access control and data exposure risks. We built Nautillo Pro for founders who care about web app security and want to simulate real attacker paths before scaling. There’s a free version available, with DNS ownership validation required so only legitimate owners can test their own applications.
Product direction looks solid. Pair it with predictable data protection, and it becomes much stronger for contractors and professionals.
Appreciate the thoughtful questions — security is definitely important when dealing with invoices and business data.
At the moment, the tool is designed to be no-signup and primarily client-side for invoice generation. We are not maintaining user accounts or storing invoice history server-side.
Invoices are generated on demand and exported directly as PDFs, which significantly reduces long-term data exposure risks.
If persistent storage or account features are introduced later, proper data isolation, access control, and secure link handling would be implemented as core architecture decisions rather than add-ons.
Thanks for raising these considerations — they’re important as the product evolves.