# Where is Observable going? **URL:** \ **Category:** Feedback\ **Created:** [May 2, 2025, 6:16am UTC](https://talk.observablehq.com/t/where-is-observable-going/10372 "2025-05-02T06:16:22Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![neocarto](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/neocarto/32/6554_2.png) [@neocarto](https://talk.observablehq.com/u/neocarto)\ **Post date:** [May 2, 2025, 6:16am UTC](https://talk.observablehq.com/t/where-is-observable-going/10372/1 "2025-05-02T06:16:22Z")
I don’t know if this is the right place to post this. But I don’t know where to put it on this forum. And I think this discussion is important. It needs to be opened. So… Notebooks, Framework and now Canevas. So many new features. But Observable cloud depreciated. Notebook gratuity, then no, then yes. So many zigzags too. Where is Observable going? I confess I don’t know anymore. For me, Notebooks are a really great tool. It’s Observable’s strong point. I love them. Notebooks create a community. They enable everyone to progress and help the ecosystem to grow. But I get the impression that it’s not evolving any more. No new libs. No new features. It’s as if the Observable core team has stopped making it a priority. I hope I’m wrong. Anyway, I think that would be a big mistake. That’s my feeling. Answers and thoughts on the situation are welcome. > **[Where is Observable going? · observablehq feedback · Discussion #654](https://github.com/observablehq/feedback/discussions/654)** > > Notebooks, Framework and now Canevas. So many new features. But Observable cloud depreciated. Notebook gratuity, then no, then yes. So many zigzags too. Where is Observable going? I confess I don't... ---
**Author:** ![tomlarkworthy](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/tomlarkworthy/32/5940_2.png) [@tomlarkworthy](https://talk.observablehq.com/u/tomlarkworthy)\ **Post date:** [May 2, 2025, 7:10am UTC](https://talk.observablehq.com/t/where-is-observable-going/10372/2 "2025-05-02T07:10:49Z")
One thing that attracted me initially to Observable was the the runtime was MIT licensed ([GitHub - observablehq/runtime: The reactive dataflow runtime that powers Observable Framework and Observable notebooks](https://github.com/observablehq/runtime)) which means that if the business failed, then there was some hope of continuity for the time I invested building software on this novel (and amazing) platform. The reason I am building a single file notebook format which does not require a server and is compatible with Observable is so that if the worst happens, I have a bunch of working, self-editable notebooks to recover from, in a format that is 100% local-first, which works the way I love. > **[Jumpgate](https://observablehq.com/@tomlarkworthy/jumpgate)** > > Jumpgate takes an ordinary notebook from Observable, mixes it with extra tooling (the frame), and exports it to a single lopecode file, which you can optionally push to Github, preview or download as an offline-first file. We use this approach to... The repository holding the source code to the file format and backup infrastructure is [here](https://github.com/tomlarkworthy/lopecode). My personal notebooks are backed up [here](https://github.com/tomlarkworthy/lopebooks). I am quite happy with using Observable as my primary code store. ~~They have communicated the notebooks will not receive new development but will stick around~~ (don’t think they actually said that, sorry for confusing things), but I also think its wise to always have an insurance policy. Lopecode is my insurance policy. If you would like to use it too and you need docs/features/support, open a ticket on the Github. ---
**Author:** ![dleeftink](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/dleeftink/32/7049_2.png) [@dleeftink](https://talk.observablehq.com/u/dleeftink)\ **Post date:** [May 2, 2025, 7:40am UTC](https://talk.observablehq.com/t/where-is-observable-going/10372/3 "2025-05-02T07:40:11Z")
Some open questions on the [Framework discussion](https://github.com/observablehq/framework/discussions/1976) board as well. In hindsight what really took some air out of the community was the flip-flopping on the notebook publishing defaults and paid plans as well as less prominently featuring trending notebooks. On the tech side, I remember the mobile editor being more stable in the past (pre 2022), as for a while it was kind of difficult to place the cursor and insert linebreaks, often jumping back and forth (Chrome Android, I’ve sinced used the mobile editor less, so this may have been fixed). I think monetisation could have been handled with a user Marketplace instead, offering plugins, templates, bespoke visualisations, etc. for others to try or buy (a bit like buying custom theming from e-commerce websites). We know from notetaking tools as Obsidian that offering a standardised plugin platform can draw in a lot of would-be users and would make userland UX modifications less hacky than they are. Larger clients would likely pay more if some form of distributed (GPU) compute was offered as an additional back-end to notebooks, to entice the model training crowd. E.g. tight integration with existing libraries, or an easy bridge to interface with other language ‘cells’ so that non-Javascript packacges could be used. Framework is on the right track here with its dataloaders, but may not offer customers much that need to distribute their compute workloads. This is where a cloud service can come in. In any case, I also am onboard with notebooks still, and hope to see them maintained in the future. ---
**Author:** ![neocarto](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/neocarto/32/6554_2.png) [@neocarto](https://talk.observablehq.com/u/neocarto)\ **Post date:** [May 2, 2025, 8:06am UTC](https://talk.observablehq.com/t/where-is-observable-going/10372/4 "2025-05-02T08:06:41Z")
> [@tomlarkworthy](#): > > he repository holding the source code to the file format and backup infrastructure is [here](https://github.com/tomlarkworthy/lopecode). My personal notebooks are backed up [here](https://github.com/tomlarkworthy/lopebooks). > > I am quite happy with using Observable as my primary code store. They have communicated the notebooks will not receive new development but will stick around, but I also think its wise to always have an insurance policy. Lopecode is my insurance policy. If you would like to use it too and you need docs/features/support, open a ticket on the Github. No new developments, this means the downfall of notebooks in the future. Will I continue to teach this to my students and continue to use notebooks myself? Not sure… I’ll have to think about it. ---
**Author:** ![neocarto](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/neocarto/32/6554_2.png) [@neocarto](https://talk.observablehq.com/u/neocarto)\ **Post date:** [May 2, 2025, 8:10am UTC](https://talk.observablehq.com/t/where-is-observable-going/10372/5 "2025-05-02T08:10:15Z")
> [@dleeftink](#): > > Some open questions on the [Framework discussion](https://github.com/observablehq/framework/discussions/1976) board as well. In hindsight what really took some air out of the community was the flip-flopping on the notebook publishing defaults and paid plans as well as less prominently featuring trending notebooks. > > On the tech side, I remember the mobile editor being more stable in the past (pre 2022), as for a while it was kind of difficult to place the cursor and insert linebreaks, often jumping back and forth (Chrome Android, I’ve sinced used the mobile editor less, so this may have been fixed). > > I think monetisation could have been handled with a user Marketplace instead, offering plugins, templates, bespoke visualisations, etc. for others to try or buy (a bit like buying custom theming from e-commerce websites). We know from notetaking tools as Obsidian that offering a standardised plugin platform can draw in a lot of would-be users and would make userland UX modifications less hacky then they are. > > Larger clients would likely pay more if some form of distributed (GPU) compute was offered as an additional back-end to notebooks, to entice the model training crowd. E.g. tight integration with existing libraries, or an easy bridge to interface with other language ‘cells’ so that non-Javascript packacges could be used. Framework is on the right track here with its dataloaders, but may not offer customers much that need to distribute their compute workloads. This is where a cloud service can come in. > > In any case, I also am onboard with notebooks still, and hope to see them maintained in the future. I think that relegating notebooks to the background is a major strategic failure. ---
**Author:** ![tomlarkworthy](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/tomlarkworthy/32/5940_2.png) [@tomlarkworthy](https://talk.observablehq.com/u/tomlarkworthy)\ **Post date:** [May 2, 2025, 10:09am UTC](https://talk.observablehq.com/t/where-is-observable-going/10372/6 "2025-05-02T10:09:43Z")
Sorry, I can’t find any evidence they said no future development. Last noteworthy thing was that they would find a way to update Notebooks to be Framework compatible but I can’t find that either. ---
**Author:** ![EE2dev](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/ee2dev/32/695_2.png) [@EE2dev](https://talk.observablehq.com/u/EE2dev)\ **Post date:** [May 2, 2025, 9:45pm UTC](https://talk.observablehq.com/t/where-is-observable-going/10372/7 "2025-05-02T21:45:02Z")
thanks @neocarto for posting this. I have the same feeling you expressed and am also evaluating how much to invest in new notebooks (which I love). Thanks @tomlarkworthy for sharing jumpgate - I will happily try it out! ---
**Author:** ![mcmcclur](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/mcmcclur/32/2364_2.png) [@mcmcclur](https://talk.observablehq.com/u/mcmcclur)\ **Post date:** [May 7, 2025, 1:24pm UTC](https://talk.observablehq.com/t/where-is-observable-going/10372/8 "2025-05-07T13:24:39Z")
> [@neocarto](#): > > For me, Notebooks are a really great tool. It’s Observable’s strong point. I love them. Notebooks create a community. They enable everyone to progress and help the ecosystem to grow. But I get the impression that it’s not evolving any more. No new libs. No new features. It’s as if the Observable core team has stopped making it a priority. I hope I’m wrong. Anyway, I think that would be a big mistake. I wrote about this at some length on [my Framework blog](https://mcmcclur.observablehq.cloud/mark-on-framework/posts/TheNotebook/). I guess that’ll be gone once Observable.cloud goes but the key points are - Observable Framework is an awesome new product that excels at producing fast, response, interactive web-based visualizations, - the Observable notebook is an older product that provides an incredible community environment for quickly prototyping the same kinds of visualizations in a notebook, and - the two products _could and should_ complement and enhance one another beautifully. By this point, we should see an Observable Notebook 2.0 with syntax that’s fully consistent with Framework. Users should be able to export their notebooks to Framework projects that are ready to be compiled to production quality websites. That setup would provide a unique path for new users to get into serious development. Tech companies have, for decades, integrated new products with existing ones to leverage their developed tech stack and user loyalty to promote those new products. The strategy has been so successful, that governments have from time to time had to intervene. In my view, it is a tremendous loss that Observable has not found a way to do that with the Notebook. * * * Having said all that, there are some truly amazingly creative folks behind Observable and the open source ecosystem surrounding it, i.e. Framework, D3, Plot, etc. That’s where my energy is going these days. ---
**Author:** ![kickout](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/kickout/32/2541_2.png) [@kickout](https://talk.observablehq.com/u/kickout)\ **Post date:** [May 8, 2025, 1:39pm UTC](https://talk.observablehq.com/t/where-is-observable-going/10372/9 "2025-05-08T13:39:12Z")
Will chime in as I’m a very causal user so I see changes late and after the fact. Notebooks, Plot have been absolute rockstar products IMO. No complaints and I have loved them. I started on D3 on my local machine and graduated to Notebooks (which had a learning curve, but it was worth it). Framework is ‘ok’; I find it confusing and non-intuitive (I am NOT a SWE). Didn’t use or understand Cloud at all. Ditto with canvas. I find it unlikely people are collaborating developing visuals (?) but am open to being wrong. I was hoping there would be a local only Notebook or some sort of standalone integrated IDE, Ala Rstudio. Will follow this thread for opinions. Thought Tomlarkworthy was a Observable employee this whole time; thanks for the help over the years Tom. ---
**Author:** ![mbostock](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/mbostock/32/9_2.png) [@mbostock](https://talk.observablehq.com/u/mbostock)\ **Post date:** [July 29, 2025, 3:03pm UTC](https://talk.observablehq.com/t/where-is-observable-going/10372/10 "2025-07-29T15:03:15Z")
Apologies for not replying sooner, but we’ve been working on next-generation notebooks and I wanted to wait until we had something meaningful to share! I posted an [Observable Notebooks 2.0 announcement thread](https://talk.observablehq.com/t/previewing-observable-notebooks-2-0/10483), but here’s a direct link to the [Observable Notebooks 2.0 Technology Preview announcement](https://observablehq.com/notebook-kit/). We’re still committed to notebooks, and appreciate your feedback! 🙏 ---
**Author:** ![mcmcclur](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/mcmcclur/32/2364_2.png) [@mcmcclur](https://talk.observablehq.com/u/mcmcclur)\ **Post date:** [August 6, 2025, 1:09am UTC](https://talk.observablehq.com/t/where-is-observable-going/10372/11 "2025-08-06T01:09:31Z")
> [@mbostock](#): > > I posted an [Observable Notebooks 2.0 announcement thread](https://talk.observablehq.com/t/previewing-observable-notebooks-2-0/10483), Did you? I get a “Oops! That page doesn’t exist or is private” message. ---
**Author:** ![mootari](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/mootari/32/581_2.png) [@mootari](https://talk.observablehq.com/u/mootari)\ **Post date:** [August 6, 2025, 6:10pm UTC](https://talk.observablehq.com/t/where-is-observable-going/10372/12 "2025-08-06T18:10:33Z")
> [@mcmcclur](#): > > I get a “Oops! That page doesn’t exist or is private” message. Sorry about that, we just made the category public. The post should be visible now. ---
**Author:** ![neocarto](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/neocarto/32/6554_2.png) [@neocarto](https://talk.observablehq.com/u/neocarto)\ **Post date:** [March 13, 2026, 10:46am UTC](https://talk.observablehq.com/t/where-is-observable-going/10372/13 "2026-03-13T10:46:33Z")
What will become of the Observable online platform? ---
**Author:** ![tophtucker](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/tophtucker/32/4781_2.png) [@tophtucker](https://talk.observablehq.com/u/tophtucker)\ **Post date:** [June 12, 2026, 7:36pm UTC](https://talk.observablehq.com/t/where-is-observable-going/10372/14 "2026-06-12T19:36:14Z")
> [@Try the new Observable today](https://talk.observablehq.com/t/try-the-new-observable-today/10698): > > “SECRET” PRE-ANNOUNCEMENT for our friends in the forum: Observable has been working on revamping notebooks on the web. It works with (almost?) all your existing notebooks, but it is also built (like Desktop) on the new open-source foundation of Notebook Kit. It has better AI, both in the notebook sidebar and as a standalone “Chat” interface where every message is a cell. And it has better community listings. It’s still missing a ton of features (private imports, database clients, minimap), but …