User:Youjung/PMOMMs: Difference between revisions
No edit summary |
|||
| (72 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Projects that may or may not be made! | Projects that may or may not be made! | ||
== Clunky Crappy Chaotic App == | |||
====== What is it? ====== | |||
Clunky Crappy Chaotic App is a service that does not provide a service. It does not improve your life but perhaps deteriorate it. | |||
== | ====== Why make it? ====== | ||
Why does all apps have to be useful? | |||
Within the app environment, slightest inconvenience feels so much more frustrating. And why does everything have to be seamless and user friendly? Every app looks the same and it feels sterile. Where is the joy of taking time to figure things out? I think there is something we learn from clunky and chaotic experience. | |||
====== Workflow ====== | |||
# List up annoying functions or useless services | |||
# Design it as fancy as possible, add unnecessary details that hinders readability | |||
# Code the app add as much as interaction as possible, make it uncomfortable | |||
# Upload it to server | |||
# Share it to others with a hooking message | |||
====== Timetable ====== | |||
{| class="wikitable" | |||
|+ | |||
!Date | |||
!Task | |||
|- | |||
|Day 1 | |||
|Research and ideation on clunky crappy chaotic services/functions | |||
|- | |||
|Day 2 | |||
|Just start making it directly on a code editor no need to design | |||
|- | |||
|Day 3 | |||
|Make it as fancy/dirty/heavy as possible | |||
|- | |||
|Day 4 | |||
|Fix bugs (but don't work too hard on it) | |||
|- | |||
|Day 5 | |||
|Come up with a hooking message to increase engagement | |||
|- | |||
|Day 6 | |||
|Share it! and ignore their feedbacks/reviews | |||
|} | |||
====== Rapid prototypes (scratches) ====== | |||
* What are the html/css functions that I've never used before? | |||
* Make a loud visual language | |||
* Do not care about readability | |||
====== Previous practice ====== | |||
<div style="display: flex;"> | |||
[[File:Ascend a website.png|thumb|400x400px|[https://munkt.github.io/stone-project/ Ascend a Website]: In order to navigate through this website you have to scroll up instead of scroll down. This project challenges the expected actions we take within digital environments.]] | |||
</div> | |||
====== Relation to a wider context ====== | |||
* What is behind the seamless interface of app services we use everyday? | |||
* Convenience is built on the sacrifice of (invisible) workers. | |||
* Why do we take convenience, usefulness for granted on digital environments? | |||
* We tend to fantasizing high tech, what are the infrastructures and costs behind it and what are we losing in this process? | |||
<br> | |||
<br> | |||
<br> | |||
== Crumbles of Reflection == | |||
====== What is it? ====== | |||
''Crumbles of reflection'' is a website where you can create a illustration with stickers. Each sticker is a drawing that represents/reflects on keywords(e.g. curiosity, serenity, resilience, anxiety, hesitation, emptiness) that can express your inner states. You select a keyword or shape you like and make a drawing or a meaning. | |||
====== Why make it? ====== | |||
Drawing something is a way of letting things out. But often times, it is difficult to start drawing. You are blocked, thinking about what to draw. ''Crumbles of Reflection'' already has a set of drawings which you can already start with. Don't overthink and just start making something. Maybe it can be like decorating your journal. It is scary draw something on your diary but it is easy to just stick something on there. | |||
====== Workflow ====== | |||
# Research and write a project description | |||
# List up keywords, ask people around you if they have any keywords they are thinking about themselves. | |||
# Draw a shape thinking about the keywords and scan them. | |||
# Make a website using canvas API add functions such as rotate, resize, delete and download | |||
# Connect to flask application where you can save the drawings | |||
# Upload it to a server | |||
# Test it out | |||
====== Timetable ====== | |||
{| class="wikitable" | |||
|+ | |||
!Date | |||
!Task | |||
|- | |||
|Day 1 | |||
|Research references and collect information about journaling | |||
|- | |||
|Day 2 | |||
|Write about the project and draw sketches of ideas | |||
|- | |||
|Day 3-4 | |||
|List up keywords and start drawing | |||
|- | |||
|Day 5 | |||
|Scan the drawings and refine them, maybe draw some more | |||
|- | |||
|Day 6 | |||
|Development: Search examples, codes using canvas API make a structure for the website | |||
|- | |||
|Day 7 | |||
|Add functions and drawings make the website work | |||
|- | |||
|Day 8 | |||
|Style the website and fix bugs | |||
|- | |||
|Day 9 | |||
|Upload the website to the server and test if it's working | |||
|- | |||
|Day 10 | |||
|Share! | |||
|- | |||
|Day 17 | |||
|Write a reflection on the project and list up improvements | |||
|} | |||
====== Rapid prototypes (scratches) ====== | |||
* How would the composed drawings look like? Would it make sense? Would it be beautiful(does it have to be)? | |||
* Figuring out canvas API, check if I can add the functions I want | |||
* How to make a gallery (having a server, figuring out flask)<br /> | |||
====== Previous practice ====== | |||
<div style="display: flex;"> | |||
[[File:DFC630C0-DB25-49F1-BADA-27273AF4EEEA 1 105 c.jpg|thumb|[[User:Youjung/paged.js|Tangled Thoughts]]: whenever youjung overthinks, she draws tangled shapes.]][[File:Screenshot 2026-04-15 at 15.35.05.png|alt=Ascend a website: stacking stones using canvas API|thumb|[https://munkt.github.io/stone-project/ Ascend a website]: stacking stones using canvas API|400x400px]]</div> | |||
====== Relation to a wider context ====== | |||
* How can I connect my pencil/analog drawing practices with what I'm doing at XPUB? | |||
* How can I make my personal drawings more collective and interactive? | |||
* How can we make drawing more easy? | |||
* How can we lower the boundary of creating something? (relating my personal struggles on overthinking on what to draw) | |||
== I like == | |||
====== What is it? ====== | |||
Images of the things(plants, signs, objects) I like in the street | |||
====== Why make it? ====== | |||
Looking at the city(Rotterdam) from a micro perspectives. Noticing small details and connect/expand them to a wider context. | |||
====== Workflow ====== | |||
# Make a flask app | |||
# Gather images together with friends | |||
# Categorize the images(plants, doors, signage, garbage, cars etc) | |||
# Find patterns and insights | |||
# Make it into a zine | |||
====== Timetable ====== | |||
{| class="wikitable" | |||
|+ | |||
!Day | |||
!Task | |||
|- | |||
|Day 1 | |||
|Make a cute website | |||
|- | |||
|Day 2 | |||
|Upload to server | |||
|- | |||
|Day 3 | |||
|Ask friends to add images | |||
|- | |||
|Day ... | |||
|Gathering | |||
|- | |||
|Day N | |||
|Find insight and think of way to how to further develop it | |||
|} | |||
====== Rapid prototypes (Scratches) ====== | |||
* Image gallery(?) | |||
* check box categorizing / how to sort the images | |||
====== Previous practice ====== | |||
* PLACES I WOULD NORMALLY NOT VISIT IN ROTTERDAM | |||
====== Relation to a wider context ====== | |||
* I want to make something cute and beautiful, even though it is trivial | |||
* Maybe it might change the way I look at the city | |||
== The search bar have it's own way 제멋대로 검색창 == | |||
====== What is it? ====== | |||
A manipulative input field that spits arbitrary answers insisting this is what I want. | |||
====== Why make it? ====== | |||
Thinking about how our inputs are interpreted according to the phrases we use. How it detects emotions and mirrors the way we talk. The more input field, the more information we are giving away to interpret us. | |||
====== Workflow ====== | |||
====== Timetable ====== | |||
====== Rapid prototypes (Scratches) ====== | |||
'''search bar(input field)''' - you type something in there | |||
'''polished answer field''' - gives you an answer | |||
'''interface of the backroom''' - shows how it breaks down your answers and interpret them in a terminal interface | |||
(can I make this?!) | |||
====== Previous practice ====== | |||
ELIZA?! | |||
====== Relation to a wider context ====== | |||
How much information are we giving away in one search, or one conversation with LLMs? | |||
How are the collected data fed back to the cycle? Are these inputs shared/sold to third party interests? | |||
How do they predict us and are we falling in their prediction? | |||
How are the AI companies earning money? What is their business model? They aren't earning money solely from subscription fees. | |||
====== '''References''' ====== | |||
https://slack.com/blog/productivity/how-search-queries-shape-better-content-and-smarter-search | |||
== Sergio! == | |||
====== What is it? ====== | |||
====== Why make it? ====== | |||
====== Workflow ====== | |||
====== Timetable ====== | |||
====== Rapid prototypes (Scratches) ====== | |||
====== Previous practice ====== | |||
====== Relation to a wider context ====== | |||
====== '''References''' ====== | |||
Latest revision as of 10:29, 3 June 2026
Projects that may or may not be made!
Clunky Crappy Chaotic App
What is it?
Clunky Crappy Chaotic App is a service that does not provide a service. It does not improve your life but perhaps deteriorate it.
Why make it?
Why does all apps have to be useful?
Within the app environment, slightest inconvenience feels so much more frustrating. And why does everything have to be seamless and user friendly? Every app looks the same and it feels sterile. Where is the joy of taking time to figure things out? I think there is something we learn from clunky and chaotic experience.
Workflow
- List up annoying functions or useless services
- Design it as fancy as possible, add unnecessary details that hinders readability
- Code the app add as much as interaction as possible, make it uncomfortable
- Upload it to server
- Share it to others with a hooking message
Timetable
| Date | Task |
|---|---|
| Day 1 | Research and ideation on clunky crappy chaotic services/functions |
| Day 2 | Just start making it directly on a code editor no need to design |
| Day 3 | Make it as fancy/dirty/heavy as possible |
| Day 4 | Fix bugs (but don't work too hard on it) |
| Day 5 | Come up with a hooking message to increase engagement |
| Day 6 | Share it! and ignore their feedbacks/reviews |
Rapid prototypes (scratches)
- What are the html/css functions that I've never used before?
- Make a loud visual language
- Do not care about readability
Previous practice
Relation to a wider context
- What is behind the seamless interface of app services we use everyday?
- Convenience is built on the sacrifice of (invisible) workers.
- Why do we take convenience, usefulness for granted on digital environments?
- We tend to fantasizing high tech, what are the infrastructures and costs behind it and what are we losing in this process?
Crumbles of Reflection
What is it?
Crumbles of reflection is a website where you can create a illustration with stickers. Each sticker is a drawing that represents/reflects on keywords(e.g. curiosity, serenity, resilience, anxiety, hesitation, emptiness) that can express your inner states. You select a keyword or shape you like and make a drawing or a meaning.
Why make it?
Drawing something is a way of letting things out. But often times, it is difficult to start drawing. You are blocked, thinking about what to draw. Crumbles of Reflection already has a set of drawings which you can already start with. Don't overthink and just start making something. Maybe it can be like decorating your journal. It is scary draw something on your diary but it is easy to just stick something on there.
Workflow
- Research and write a project description
- List up keywords, ask people around you if they have any keywords they are thinking about themselves.
- Draw a shape thinking about the keywords and scan them.
- Make a website using canvas API add functions such as rotate, resize, delete and download
- Connect to flask application where you can save the drawings
- Upload it to a server
- Test it out
Timetable
| Date | Task |
|---|---|
| Day 1 | Research references and collect information about journaling |
| Day 2 | Write about the project and draw sketches of ideas |
| Day 3-4 | List up keywords and start drawing |
| Day 5 | Scan the drawings and refine them, maybe draw some more |
| Day 6 | Development: Search examples, codes using canvas API make a structure for the website |
| Day 7 | Add functions and drawings make the website work |
| Day 8 | Style the website and fix bugs |
| Day 9 | Upload the website to the server and test if it's working |
| Day 10 | Share! |
| Day 17 | Write a reflection on the project and list up improvements |
Rapid prototypes (scratches)
- How would the composed drawings look like? Would it make sense? Would it be beautiful(does it have to be)?
- Figuring out canvas API, check if I can add the functions I want
- How to make a gallery (having a server, figuring out flask)
Previous practice
Relation to a wider context
- How can I connect my pencil/analog drawing practices with what I'm doing at XPUB?
- How can I make my personal drawings more collective and interactive?
- How can we make drawing more easy?
- How can we lower the boundary of creating something? (relating my personal struggles on overthinking on what to draw)
I like
What is it?
Images of the things(plants, signs, objects) I like in the street
Why make it?
Looking at the city(Rotterdam) from a micro perspectives. Noticing small details and connect/expand them to a wider context.
Workflow
- Make a flask app
- Gather images together with friends
- Categorize the images(plants, doors, signage, garbage, cars etc)
- Find patterns and insights
- Make it into a zine
Timetable
| Day | Task |
|---|---|
| Day 1 | Make a cute website |
| Day 2 | Upload to server |
| Day 3 | Ask friends to add images |
| Day ... | Gathering |
| Day N | Find insight and think of way to how to further develop it |
Rapid prototypes (Scratches)
- Image gallery(?)
- check box categorizing / how to sort the images
Previous practice
- PLACES I WOULD NORMALLY NOT VISIT IN ROTTERDAM
Relation to a wider context
- I want to make something cute and beautiful, even though it is trivial
- Maybe it might change the way I look at the city
The search bar have it's own way 제멋대로 검색창
What is it?
A manipulative input field that spits arbitrary answers insisting this is what I want.
Why make it?
Thinking about how our inputs are interpreted according to the phrases we use. How it detects emotions and mirrors the way we talk. The more input field, the more information we are giving away to interpret us.
Workflow
Timetable
Rapid prototypes (Scratches)
search bar(input field) - you type something in there
polished answer field - gives you an answer
interface of the backroom - shows how it breaks down your answers and interpret them in a terminal interface
(can I make this?!)
Previous practice
ELIZA?!
Relation to a wider context
How much information are we giving away in one search, or one conversation with LLMs?
How are the collected data fed back to the cycle? Are these inputs shared/sold to third party interests?
How do they predict us and are we falling in their prediction?
How are the AI companies earning money? What is their business model? They aren't earning money solely from subscription fees.
References
https://slack.com/blog/productivity/how-search-queries-shape-better-content-and-smarter-search