I tagged in one of our lead engineers to talk about the tech stack, but can chime in re: considerations for multi-platform.
We are sprinting as fast as we can to get an Android app out the door. We're also planning on investing more in the reader experience on web. Some time ago, we launched a web reader (reader.substack.com) in beta and have some exciting ideas in the works to evolve that surface.
Beyond Android, when it smaller platforms like iPad / Desktop apps, it's mostly a matter of looking at the data and listening to users. With a small team, we have to be judicious with prioritization, and as we increase the surface area for readers it's important that the experience for writers remains clear (right now their readers can already read on email, web, and mobile).
We are sprinting as fast as we can to get an Android app out the door. We're also planning on investing more in the reader experience on web. Some time ago, we launched a web reader (reader.substack.com) in beta and have some exciting ideas in the works to evolve that surface.
Beyond Android, when it smaller platforms like iPad / Desktop apps, it's mostly a matter of looking at the data and listening to users. With a small team, we have to be judicious with prioritization, and as we increase the surface area for readers it's important that the experience for writers remains clear (right now their readers can already read on email, web, and mobile).