We (the authors of the Solara web app framework) were inspired by the OpenAI keynote Wanderlust app they demoed and rebuilt it in Python using Solara.
It would be good to showcase our framework's power and inspire others to build UI's with AI/LLM elements in it.
My dream is to have a real AI-powered travel agent that would do all the discovery stuff per my constraints and selections and then book reservations (where needed) for anything. The AI agent would fill out all the necessary online forms or make calls and collect confirmations. Then it would present me with my itinerary which I can ask it to change at any time.
These days I purposefully avoid as much travel research as possible, and intently choose to immerse in the place and moment instead. I'm happy to miss that 4.97 stars dinner place, and instead enjoy interacting with a less-than-Instagram-perfect dinner & perhaps some flesh-and-bones human company.
I'm not sure this dichotomy isn't false. I can enjoy the best restaurants a city has to offer without Instagram having anything to do with it, and research doesn't preclude me from having flesh-and-bones company. There may be a good argument for not doing research, but I don't think these are it.
Possibly. I'm alluding to the spiritual disposition that expects 4.97 stars or bust. In relationship terms this often maps to expecting the perfect dinner company. When the actual company disappointingly fails to meet that standard, they are summarily dismissed, and the whole experience turns into superficial theater of appearances.
Yeah, that's definitely a phenomenon that can be harmful, as you describe. Still, this seems to be going from one extreme to the other. I guess "everything in moderation" is good advice here too.
But how much are you willing to pay for this service?
because it's not like human travel agents don't exist today, just like human drivers exist today. Does having an AI book the tickets for you meaningfully change the things for you, the customer?
>Does having an AI book the tickets for you meaningfully change the things for you, the customer?
Of course it does. You don't think replacing humans in the full service travel industry wouldn't drive down costs and upgrade capabilities and experience could be a thing?
The industry, obviously. How does that affect the customer experience though? If call up my travel agent and have them book a vacation for me, what's the difference between that and calling TravelGPT and having it book a vacation for me?
I’m curious what are you thinking the advantages of using an AI only agent for this? For example, compared to Anywhere.com, where human experts are the agents.
I just took a look at it. Seems to focus only on a handful of international spots plus now it's asking me to book a 30 minute meeting with someone. I don't mind filling in preferences and whatnot, but once you introduce a human to the mix I feel like i'm at the whim and mercy of that 1 person with their skillset, communication ability, attitude, business motivations, etc.
You do realize though that in terms of the business model, having the AI partner with select resorts and tour guides is a much more lucrative business model for the AI tour planning company?
In the end, you'll end up with Booking.com with extra steps:
"Perfect, ugh123! I've got just the hotel for you! It's the Marriott Grand Paradise, our top partner hotel. It is only 45 miles away from the specific address you requested and just barely $150 over budget per night, but they have a 4.9 rating, and with their Top Partner status, you earn 10 BookiePoints by booking there. Hurry, 33 people have booked a room there in the last hour! Do you confirm? Whoops, one more booking just now, only one room left! Do you want to save yours now?"
Did you also use help from LLMs in coding this app instead of just coding it all by hand? Just curious.
I am finding myself reaching for GPT4 more often to spin up POC apps.
You could fine-tune a coding assistant on your library and good quality example apps with documentation ... and that might take the ease of churning out new demos and apps to the next level?
It can be used for general purposes, but we focus on the data science landscape. However, our main website is built using solara, and we know a few startups using solara for their main product (public-facing, not internal).
* Solara will not continuously re-execute your script as Streamlit does.
* Solara will re-execute components instead, only what needs to.
* State in Solara is separate from the UI components, unlike streamlit, where they are strongly linked.
* State can be on the application level (global) for simplicity or on the component level (local) for creating reusable components.
* Solara should not block the render loop. Long-running functions should be executed in a thread using use_thread.
Co-creator of Voila here. Voila is rather un-opinionated about what you can run in it. While it offers excellent support for ipywidgets, it's certainly not confined to that. One downside of Voila is that it can be resource-intensive, as it creates a new kernel/process for each page view or browser tab.
Mercury, in my view, seems really interesting for quick demos and reports. It's somewhat akin to Streamlit, making it ideal for notebook authors.
On the other end of the spectrum (and pardon my shameless plug here), there's Solara (https://github.com/widgetti/solara/). Solara is a fully-fledged web framework for Python, specifically designed to handle app sizes that surpass what Streamlit and Dash can manage. It's worth noting that Solara can render ipywidgets, using a pure Python React-like framework. This can be particularly useful after the exploration phase, when you're looking to transition a project from the notebook into production.
In Solara you can dynamically put together the UI like in react, in pynecone you need to use their primitives to make lists and conditional rendering.
Also, state management is not tied to solara, but could use dataclasses or pydantic, wrapped in a reactive variable.
I think what sets Solara apart from the rest is that we use a 10 year proven paradigm, React, but on the Python side, although with a more Pythonic API.
For instance making reusable components in Python is a real benefit.
Pynecone uses ReactJS in the front end, but on the Python side it’s their own API.
I do like pynecone, their API is pretty. I do wonder with many of these frameworks. Does the paradigm works for more complex apps, or does it end in complexity hell once you go past the hello world examples. At least React has proven itself.
> For instance making reusable components in Python is a real benefit.
I think that could be a big benefit for us because we ran into problems when we wanted to create a custom component for a different Data Grid in Pynecone. In particular we tried to wrap AG Grid but ran into problems when we tried to change the styling because we couldn't overwrite the DIV element's class. Is that something that would be possible in Solara?
What Data Grids do you currently provide in Solara?
I tried to look at your Components API docs at https://solara.dev/docs/api but that's currently returning an error:
> "No object with name Page found for /opt/render/project/src/.venv/lib/python3.9/site-packages/solara/website/pages/docs/__init__.py We did find: 'Path' or 'generate_routes_directory' or 'title' or 'HERE' or 'routes'"
