Client
Codeanywhere
Year
2016 – 2017
Role
Lead Product Designer
Key Contributions
Research, UX/UI, Information Architecture, Design System
3,000+
User ratings on SaaSworthy
4.7★
Average rating across review platforms
10+ years
In active development
Codeanywhere was already live as a cloud IDE when I joined — a product used by developers worldwide to write, edit, and run code from any browser without local setup. The desktop version existed as an MVP. It needed to grow into a serious development environment for complex, professional workflows.
The mobile version didn’t exist at all.
The design challenge wasn’t to build two versions of the same product. It was to recognise that a cloud IDE on mobile is not a smaller cloud IDE on desktop — and to design each surface accordingly. Desktop is where developers live: long sessions, complex file structures, multi-language projects, Git workflows. Mobile is the second screen: quick edits between meetings, code review on the go, debugging a production issue from a phone. Different jobs. Different interfaces. One product.
I evaluated a range of cloud and desktop IDEs — including Codio, NetBeans, Eclipse, and Android Studio — to map where the market was leaving gaps. The pattern across all of them was consistent: products were either desktop-first with no cross-device story, cloud-native but education-focused rather than built for professional workflows, or mobile development tools with no general-purpose IDE. None offered a credible mobile companion alongside a full-depth desktop environment. That gap was the opening Codeanywhere could occupy.

Mobile is not a smaller desktop.
Desktop is the primary development environment — long sessions, full file trees, Git integration, terminal access, multi-language containers. Mobile is a short-burst tool sized to a different job: reviewing a diff, fixing a syntax error, checking a deployment, responding to a production alert between meetings.
Designing mobile as a responsive version of the desktop would have produced a product that served neither job well. The decision — grounded in research into how developers actually used IDEs away from their desks — was to build two distinct interfaces, each sized to the workflow it actually needs to support, inside one product.
Building on the MVP, I enhanced the desktop environment for complex professional workflows. The key additions: multi-file project support, version control with a fully integrated Git client, a modular workspace, and real-time collaboration. Server integration covers SSH/SFTP, FTP, and FTPS — developers can connect directly to remote servers and edit files or open a terminal in-browser without switching tools.
Preconfigured containers — Angular JS, Backbone.js, PHP, WordPress, and more — spin up in seconds with the right stack preloaded. The web-based terminal provides full SSH access to containers and remote servers without leaving the browser.

I designed the mobile app from scratch, concentrating on the three jobs mobile developers actually need to do away from their desk: quick edits, debugging, and script execution.
The interface is content-first: the code editor and terminal take priority, navigation is accessible without competing for screen space. Syntax highlighting, touch-friendly controls, a code diff view with red/green changes, and real-time collaboration keep the mobile app connected to the desktop workflow without trying to replicate it.
Six screens. Each one sized to a specific mobile use case. None of them a shrunk desktop view.

I ran usability sessions with developers across both platforms. Three changes came directly from that feedback: touch targets and navigation adjusted for single-hand mobile use; container management simplified on smaller screens; keyboard shortcuts and terminal behaviour refined for desktop power users who expected parity with native IDEs.
Codeanywhere shipped both products. The desktop became the primary cloud IDE for developers who wanted a full environment without local setup — used by teams worldwide across languages, frameworks, and server stacks. The mobile app became the second screen: code review, quick fixes, and emergency debugging away from the desk.
The product is still live and actively developed — most recently expanding into AI-assisted coding with a Continue.dev integration, positioning Codeanywhere as a cloud IDE for the next generation of developer tooling.
