black-forest-labs/FLUX.2-dev
Image-to-Image
•
Updated
•
97.9k
•
•
1.16k
mav·er·ick [ˈmav(ə)rɪk]
Joyapeee
·
AI & ML interests
None yet
Recent Activity
liked
a model
about 1 month ago
black-forest-labs/FLUX.2-dev
published
a model
3 months ago
Joyapeee/nuevo
updated
a model
3 months ago
Joyapeee/nuevo
Organizations
liked
a
model
about 1 month ago
published
a
model
3 months ago
updated
a
model
3 months ago
published
a
model
3 months ago
liked
6
Spaces
7 months ago
FaceSwapinHighQualitySWAPnet
📈
9
Swap faces in images
Flux IP Adapter
🖼
169
Prompt with Images in flux[dev]
Interior AI Designer
🏠
61
Ikea could never
Controlnet for Interior Design
🔥
253
Upload an image and edit it using segmentation, inpainting, or regeneration
OmniConsistency
🚀
215
Generate styled image from reference image and external LoRA
KEEP
🏢
44
Official demo of KEEP (ECCV'24) for face video SR
liked
a
Space
8 months ago
liked
a
model
8 months ago
liked
2
Spaces
8 months ago
liked
2
models
9 months ago
liked
2
Spaces
9 months ago
liked
a
model
9 months ago
reacted to
abidlabs's
post with ❤️
9 months ago
Post
3899
JOURNEY TO 1 MILLION DEVELOPERS
5 years ago, we launched Gradio as a simple Python library to let researchers at Stanford easily demo computer vision models with a web interface.
Today, Gradio is used by >1 million developers each month to build and share AI web apps. This includes some of the most popular open-source projects of all time, like Automatic1111, Fooocus, Oobabooga’s Text WebUI, Dall-E Mini, and LLaMA-Factory.
How did we get here? How did Gradio keep growing in the very crowded field of open-source Python libraries? I get this question a lot from folks who are building their own open-source libraries. This post distills some of the lessons that I have learned over the past few years:
1. Invest in good primitives, not high-level abstractions
2. Embed virality directly into your library
3. Focus on a (growing) niche
4. Your only roadmap should be rapid iteration
5. Maximize ways users can consume your library's outputs
1. Invest in good primitives, not high-level abstractions
When we first launched Gradio, we offered only one high-level class (gr.Interface), which created a complete web app from a single Python function. We quickly realized that developers wanted to create other kinds of apps (e.g. multi-step workflows, chatbots, streaming applications), but as we started listing out the apps users wanted to build, we realized what we needed to do:
Read the rest here: https://x.com/abidlabs/status/1907886
5 years ago, we launched Gradio as a simple Python library to let researchers at Stanford easily demo computer vision models with a web interface.
Today, Gradio is used by >1 million developers each month to build and share AI web apps. This includes some of the most popular open-source projects of all time, like Automatic1111, Fooocus, Oobabooga’s Text WebUI, Dall-E Mini, and LLaMA-Factory.
How did we get here? How did Gradio keep growing in the very crowded field of open-source Python libraries? I get this question a lot from folks who are building their own open-source libraries. This post distills some of the lessons that I have learned over the past few years:
1. Invest in good primitives, not high-level abstractions
2. Embed virality directly into your library
3. Focus on a (growing) niche
4. Your only roadmap should be rapid iteration
5. Maximize ways users can consume your library's outputs
1. Invest in good primitives, not high-level abstractions
When we first launched Gradio, we offered only one high-level class (gr.Interface), which created a complete web app from a single Python function. We quickly realized that developers wanted to create other kinds of apps (e.g. multi-step workflows, chatbots, streaming applications), but as we started listing out the apps users wanted to build, we realized what we needed to do:
Read the rest here: https://x.com/abidlabs/status/1907886