Description
This internal application I developed manages customer systems and supports developers’ daily workflows, including code deployment. Over six months, I created and refined this feature-packed tool to streamline operations and enhance efficiency.
Role
Front-end developer, and UX designer
Techstack
Svelte
Tauri
AWS
JavaScript
Tailwind
These images are mockups made in Figma, and does not look exactly like the real product.
Features
Most Frequently Used
Automate code deployment, testing, and blue-green deployments. The “Deploy” button triggers these processes, ensuring efficient, reliable, and smooth transitions to production.
Enables authorized DevOps team members to connect to and manage AWS RDS instances. It supports tasks like monitoring and maintenance, with restricted access to ensure secure, role-based usage.
Dialog for managing customer systems, including enabling features, activating or deactivating modules, modifying licenses, and viewing customer data.
Dialog for managing customer systems, including enabling features, activating or deactivating modules, modifying licenses, and viewing customer data.
Setbacks
Obstacles Faced
The biggest challenge was managing the balance between adding critical features requested by stakeholders and adhering to strict deadlines. This required careful prioritization and clear communication with the team to ensure that the most impactful features were delivered on time.
Setting up the CI/CD workflow tools was particularly challenging due to the need to ensure compatibility with the company’s existing infrastructure. There were initial setbacks in automating deployment processes, but these were resolved by closely collaborating with DevOps teams to refine the pipeline.
Ensuring secure and role-based access for interacting with AWS RDS was complex. Implementing granular permissions required significant testing to avoid accidental privilege escalation while keeping the interface user-friendly.
Reflections
Insights Gained
Regular feedback from internal users proved invaluable. Iterating based on their input significantly improved the tool’s usability, leading to higher adoption rates among the staff.
Planning for potential future features during the initial design phase saved significant time. For example, building modular components allowed new features to be added with minimal disruption to the existing codebase.
Collaborating with different teams, such as DevOps and IT, emphasized the importance of cross-functional communication. This collaboration not only sped up development but also ensured that the tool met the diverse needs of its users.
Not Available
Not Available
Like what you see?
Get in touch
Inspired by ishanipandey