I haven't used Iced but re. Dioxus, I don't know if it's necessary more verbose conceptually. One of the most frustrating things with React is handling async updates, and while Rust's async story is conceptually difficult, it's ultimately much easier to reason about (imo). Like are we sure a comparable component in React would be any less verbose?

   let mut breed = use_signal(|| "hound".to_string());

   let dogs = use_resource(move || async move {
     reqwest::Client::new()
       .get(format!("https://dog.ceo/api/breed/{breed}/images"))
       .send()
       .await?
       .json::<BreedResponse>()
       .await
   });

   rsx! {
     input {
       value: "{breed}",
       oninput: move |e| breed.set(e.value()),
     }

     div {
       display: "flex",
       flex_direction: "row",
       if let Some(response) = &*dogs.read() {
         match response {
           Ok(urls) => rsx! {
             for image in urls.iter().take(3) {
               img {
                 src: "{image}",
                 width: "100px",
                 height: "100px",
               }
             }
           },
           Err(err) => rsx! { "Failed to fetch response: {err}" },
         }
       } else {
         "Loading..."
       }
     }
   }