An Introduction and Open Discussion

Hello Everyone!

First off, I’m new to the forum, please feel free to message me.

I’m a software developer, have a passion for it (technology in general as well as design and engineering), and Bolt.New/OTTODEV is awesome, and I love to see the almost daily improvements!

Anyone try out QwQ? It’s actually impressively good (may be a first impression bias).

It one-shotted a prompt that Qwen2.5-Coder-32B-Instruct had problems with. It’s a little slower than the Coder version but it’s supposed to be a “reasoner” of sorts. And I did nothing special to add it, just made another entry in the “~/app/utils/constants.ts” file.

It just fails to acknowledge it has access to the terminal or files, lol. I’m not really sure why this is, but I’ll find out.

Having a lot of fun customizing this thing and I’d like to make it my daily driver, but it’s still lacking a lot of features. And I’d like to have that discussion, aka. what features to add from here. For one, I think the UI/X should be more like StackBlitz (company that makes Bolt.New, so it makes sense. But the mobile version is much cooler (gestures, intuitive, etc.)

I could see myself doing full development on my phone, which is both amazing and I never thought would have even crossed my mind. Take the bug, carpool, or an autonomous ride for say an hour commute and complete a full stack app on your phone within that time – so crazy.

vitejs/awesome-vite - StackBlitz

Welcome @aliasfox! Thanks for introducing yourself and it’s great to meet you!

What’s your background as a software engineer? :slight_smile:

I’ve had a similar experience with QwQ where it’s an awesome model but never actually produces artifacts for the webcontainer. I’ve also had it get stuck in infinite reasoning loops which I haven’t had with another local LLM in a long time.

Improving the UI/UX is certainly important! What other features do you have in mind?

1 Like

Oh, I’ve gotten Qwen models in infinite loops pretty recently, spitting out nonsense and non-English as well, lol.

I used to work for a few web-development companies, mostly contributed with building their eCommerce’s platform from the ground up. Did a bit of graphic design as well. Done a lot of .net/ASPX, PHP, and I love Python (ML/Data Science). New to a bit of the web technology, but I’m loving Vite and the automation testing (linting, etc.). Crashed coursed into Typescript (new to me) and I have a strong background in JavaScript (but it’s a big ecosystem to wrap your head around now, lol).

I’ve had a lot of roles, but right now my specific job title is GIS Developer for a fortune 500 Oil and Gas company. I’ve been re-writing and refactoring a lot of their code base. Most of their web stack is angular and they have a lot of Python (migrating everything from Python2 to Python3). There’s a lot of ESRI toolboxes they use that depend on the Python code base and whatnot.

I was thinking of getting an automatic oTToTest deployment running that will build the site with all PR’s that have passed, for testing. Might introduce some breaking changes (but it’s a testing site, so whatevs) but could lead to faster and easier development. Might do something similar for staging/stable that requires a sign off. Basically, get as close to realistically automating deployments with some checks and balances. Once AI can do all the UI and user testing, it will be, lol.

As for improvements to the core oTToDev:

  • UI Overhaul:
  • Closer to StackBlitz WebContainers mobile UI with a few tweaks and improvements (that’s another discussion; see attached screenshots and notes below)
  • Right click context menu
  • Default to Dark Theme mode
  • More Mobile responsive
  • Extract “PROVIDER_LIST” from app/utils/constants.ts and make a UI tool to edit them.
  • Support for a Theme selector (community could compete for best UI/X, simply offer choices, or for special use cases/customization without a global override)?

Note: I want it to always be in the editor view personally with maybe a login landing page (with profiles, settings, etc). But that might just be me. Needs a sidebar discussion and brainstorm perhaps.

Terminal

  • Git Support (through wrapper around “isomorphic-git” npm package)
  • Copy/Paste (Done, pending PR)
  • Needs help documentation (what commands are available, etc.)
  • Python pypi/pip package support

Note: Hear me out: every command should be available in the terminal and setup as a call function (shared functions). The code could be re-used for the UI elements, so that everything stays consistent. Makes maintaining code easier, allows for scripting anything, and gives AI access to all commands.

Other:

  • Add PWA Support (native feel on mobile, caching, etc.)
  • Collaborate editing
  • RAG Integration
  • QwQ Reasoning (wrapper for core LLM)
  • Fix document formatting
  • Show history (like PyCharm)
  • Show Stats (it/s, latency, etc.)
  • Finetune System Prompts (a whole other conversation)
  • Exclusively use starting Templates (Tailwind, Astro, GitIgnore, etc.) to improve success rate of AI.
  • Document and Project management features
  • Ability to find/search files/folders
  • Extensive documentation (wiki, tutorials, etc.)

GitHub (maybe helpful):

  • Enable Discussion, Wiki,
  • Security Options (Dependabot, Code/Secret Scanning, etc.)
  • Project Management, etc.

Bug fixes and clean up code, logic, and whatnot… maybe compare document feature, team chat, plugins, integrations, etc.

Stackblitz Mobile Screenshots:

Note: Really nice but needs UI improvements, PWA features, full slide out menu, more gestures, terminals should tab and not split, etc.

Right click context menu, with WYSIWYG context editing:

1 Like

@aliasfox WOW I really appreciate all the time and effort you put into this! And I couldn’t agree with you more for each of these features. They would all be awesome additions to oTToDev and honestly many of them crucial for oTToDev to truly be what we want it to.

Would you ever consider contributing to implement any of these?

1 Like

I would definitely like to. If I could, I’d like to make this app my daily driver and would love to contribute to making it amazing. Right now, most of my time has been spent with figuring out infrastructure and jumping headfirst into n8n. And a lot of reading and research, lol.

I ran into issues using HuggingFace’s free Serverless endpoints and reliability, so I started getting serious and started using OpenRouter… best cost I found for the features. If I need more throughput, I’ll likely use Groq.

I’m going to spin up a VPS to self-host/run n8n (wasn’t happy with their offerings) and the idea is to point it’s output directly into oTToDev for full customization of the LLM workflow.

It might be a bit of an overhaul, but I think it might be useful to have a theme selector. The idea would be to separate out the UI elements into “theme packages” and it would be easier for your average user to create themes (off of say a template), maybe vote on them, etc.

But before I added anything substantial, I would like to see some of the PR’s be merged to main (lot of cool changes people are working on). I’m really interested in the PR #572 when it gets finalized.

1 Like