|
66945
|
🤑🤑 by @r96383873 | Stardance
|
r96383873
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 🤑🤑 by @r96383873 | Stardance
|
1792464502.8587842
|
1793069302.8587842
|
|
47945
|
🛰️ Simulador de encuentros orbitales by @lautaroXC 🛰️ Simulador de encuentros orbitales by @lautaroXC7 | Stardance...
|
lautaroXC7
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 🛰️ Simulador de encuentros orbitales by @la Title: 🛰️ Simulador de encuentros orbitales by @lautaroXC7 | Stardance...
|
1792533190.038408
|
1793137990.038408
|
|
35937
|
🛬 by @Noctix | Stardance
|
Noctix
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 🛬 by @Noctix | Stardance
|
1792482655.703514
|
1793087455.703514
|
|
45014
|
🚀 Shaheer's Space Tab by @shaheer | Stardance
|
shaheer
|
1
|
0.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-07T20:54:04Z", "hours": 0.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "🚀 SpaceTab < A simple space-themed new-tab page powered by NASA’s Astronomy Picture of the Day API. => 🌐 Live Demo https://shaheerbro.github.io/SpaceTab/ =>✨ Features 🌌 NASA Astronomy Picture of the Day 🎨 Custom space-themed design ⚡ JavaScript functionality 📱 Responsive layout => 🛠️ Built With: HTML, CSS, JavaScript, NASA API, GitHub Pages => 🚀 Make Your Own Download or clone this repository. Open the folder in VS Code. Edit index.html for the page structure. Edit style.css for the design. Edit script.js for the functionality. Open index.html in your browser by right clicking it and click open in browser. Made by shaheer for Hack Club Stardance. Thanks for checking out SpaceTab! 🚀 :)", "repo": "https://github.com/shaheerbro/SpaceTab", "demo": "https://shaheerbro.github.io/SpaceTab/"}]...
|
[{"post_id": 42610, "ts": "202 [{"post_id": 42610, "ts": "2026-08-07T13:01:35Z", "hours": 0.2625, "text": "This is my first prototype of SpaceTab, and I’ve been working on it for quite a while. At the beginning, I didn’t know that you could track your time while working on projects. Later, I found out about Hackatime, created my account, and connected it to VS Code. After setting everything up, I spent about 15 minutes working on and improving my SpaceTab project while tracking my time. This is my first project on Stardance, and I’m really happy with how it turned out. I’m hoping to earn some Stardust so I can start making more projects and eventually get some cool materials to build even more things. I really like Stardance because it’s a great place to make projects, learn new things, and get help from other people in the community. Thanks, Stardance! 🚀✨"}]...
|
Title: 🚀 Shaheer's Space Tab by @shaheer | Sta Title: 🚀 Shaheer's Space Tab by @shaheer | Stardance
Devlogs:
This is my first prototype of SpaceTab, and I’ve been working on it for quite a while. At the beginning, I didn’t know that you could track your time while working on projects. Later, I found out about Hackatime, created my account, and connected it to VS Code. After setting everything up, I spent about 15 minutes working on and improving my SpaceTab project while tracking my time. This is my first project on Stardance, and I’m really happy with how it turned out. I’m hoping to earn some Stardust so I can start making more projects and eventually get some cool materials to build even more things. I really like Stardance because it’s a great place to make projects, learn new things, and get help from other people in the community. Thanks, Stardance! 🚀✨
Ships:
🚀 SpaceTab < A simple space-themed new-tab page powered by NASA’s Astronomy Picture of the Day API. => 🌐 Live Demo https://shaheerbro.github.io/SpaceTab/ =>✨ Features 🌌 NASA Astronomy Picture of the Day 🎨 Custom space-themed design ⚡ JavaScript functionality 📱 Responsive layout => 🛠️ Built With: HTML, CSS, JavaScript, NASA API, GitHub Pages => 🚀 Make Your Own Download or clone this repository. Open the folder in VS Code. Edit index.html for the page structure. Edit style.css for the design. Edit script.js for the functionality. Open index.html in your browser by right clicking it and click open in browser. Made by shaheer for Hack Club Stardance. Thanks for checking out SpaceTab! 🚀 :)...
|
1792842723.0408678
|
1792929123.0408678
|
|
24804
|
🚀 NASA Space Lines by @duarda350 | Stardance
|
duarda350
|
1
|
4.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-23T13:54:30Z", "hours": 4.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "🛰️ NASA API Integration The project uses NASA’s Astronomy Picture of the Day API. API endpoint: https://api.nasa.gov/ The API key is provided at runtime using Flutter’s –dart-define mechanism. Example: flutter run -d chrome –dart-define=NASA_API_KEY=YOUR_API_KEY Important Do not commit your NASA API key to GitHub. The project intentionally reads the API key using: const apiKey = String.fromEnvironment(‘NASA_API_KEY’); This keeps the key outside the source code. Note: because this project runs on Flutter Web, values passed with –dart-define can ultimately be exposed in the client application. For a production application, a backend/proxy and appropriate API restrictions should be considered. 🛠️ Technologies Technology Purpose Flutter Application framework Dart Programming language Flutter Web Web application runtime Material Design UI components NASA APOD API Astronomy data and media HTTP API communication JSON API data format VS Code Development environment Git Version control GitHub Source code repository 📂 Project Structure Nasa_Space_Trip_App/ │ ├── android/ ├── ios/ ├── linux/ ├── macos/ ├── web/ ├── windows/ │ ├── assets/ │ └── imagens/ │ ├── background.jpg │ ├── iss.png │ ├── mars.png │ ├── moon.png │ ├── neptune.png │ ├── saturn.png │ └── sun.png │ ├── lib/ │ ├── screens/ │ │ ├── data/ │ │ │ └── planets.dart │ │ │ │ │ ├── body_screen.dart │ │ ├── home_screen.dart │ │ └── planet_detail_screen.dart │ │ │ ├── services/ │ │ └── nasa_service.dart │ │ │ └── main.dart │ ├── test/ │ ├── pubspec.yaml ├── pubspec.lock ├── analysis_options.yaml └── README.md 🧭 Traceability / Setup Table The table below provides a quick traceability guide for developers who want to run, understand, or troubleshoot the project. Step Component Location Purpose Verification 1 Flutter SDK Local environment Provides the development framework flutter –version 2 Project dependencies pubspec.yaml Defines project packages flutter pub get 3 Assets assets/imagens/ Stores application images Check image files exist 4 Main entry point lib/main.dart Starts the application Run the project 5 Home screen lib/screens/home_screen.dart Application landing screen Home screen appears 6 Destination screen lib/screens/body_screen.dart Displays available destinations Destination list appears 7 Planet data lib/screens/data/planets.dart Stores destination information Destination cards load 8 Detail s", "repo": "https://github.com/mariaeduardabuenoda/Nasa_Space_Trip_App.", "demo": "https://mariaeduardabuenoda.github.io/Nasa_Space_Trip_App./"}]...
|
[{"post_id": 72663, "ts": "202 [{"post_id": 72663, "ts": "2026-09-23T13:31:43Z", "hours": 4.3619, "text": "🚀 NASA Space Lines NASA Space Lines is a space exploration application developed with Flutter and Dart.The project allows users to explore different space destinations, view information about planets and the International Space Station (ISS), access NASA’s Astronomy Picture of the Day (APOD), and calculate how much they would weigh on different celestial bodies.The application was developed as a practical project to improve mobile and web application development skills, API integration, UI development, state management, and problem-solving with Flutter. Click here to see the repository , click here to view the page ."}]...
|
Title: 🚀 NASA Space Lines by @duarda350 | Stardanc Title: 🚀 NASA Space Lines by @duarda350 | Stardance
Devlogs:
🚀 NASA Space Lines NASA Space Lines is a space exploration application developed with Flutter and Dart.The project allows users to explore different space destinations, view information about planets and the International Space Station (ISS), access NASA’s Astronomy Picture of the Day (APOD), and calculate how much they would weigh on different celestial bodies.The application was developed as a practical project to improve mobile and web application development skills, API integration, UI development, state management, and problem-solving with Flutter. Click here to see the repository , click here to view the page .
Ships:
🛰️ NASA API Integration The project uses NASA’s Astronomy Picture of the Day API. API endpoint: https://api.nasa.gov/ The API key is provided at runtime using Flutter’s –dart-define mechanism. Example: flutter run -d chrome –dart-define=NASA_API_KEY=YOUR_API_KEY Important Do not commit your NASA API key to GitHub. The project intentionally reads the API key using: const apiKey = String.fromEnvironment(‘NASA_API_KEY’); This keeps the key outside the source code. Note: because this project runs on Flutter Web, values passed with –dart-define can ultimately be exposed in the client application. For a production application, a backend/proxy and appropriate API restrictions should be considered. 🛠️ Technologies Technology Purpose Flutter Application framework Dart Programming language Flutter Web Web application runtime Material Design UI components NASA APOD API Astronomy data and media HTTP API communication JSON API data format VS Code Development environment Git Version control GitHub Source code repository 📂 Project Structure Nasa_Space_Trip_App/ │ ├── android/ ├── ios/ ├── linux/ ├── macos/ ├── web/ ├── windows/ │ ├── assets/ │ └── imagens/ │ ├── background.jpg │ ├── iss.png │ ├── mars.png │ ├── moon.png │ ├── neptune.png │ ├── saturn.png │ └── sun.png │ ├── lib/ │ ├── screens/ │ │ ├── data/ │ │ │ └── planets.dart │ │ │ │ │ ├── body_screen.dart │ │ ├── home_screen.dart │ │ └── planet_detail_screen.dart │ │ │ ├── services/ │ │ └── nasa_service.dart │ │ │ └── main.dart │ ├── test/ │ ├── pubspec.yaml ├── pubspec.lock ├── analysis_options.yaml └── README.md 🧭 Traceability / Setup Table The table below provides a quick traceability guide for developers who want to run, understand, or troubleshoot the project. Step Component Location Purpose Verification 1 Flutter SDK Local environment Provides the development framework flutter –version 2 Project dependencies pubspec.yaml Defines project packages flutter pub get 3 Assets assets/imagens/ Stores application images Check image files exist 4 Main entry point lib/main.dart Starts the application Run the project 5 Home screen lib/screens/home_screen.dart Application landing screen Home screen appears 6 Destination screen lib/screens/body_screen.dart Displays available destinations Destination list appears 7 Planet data lib/screens/data/planets.dart Stores destination information Destination cards load 8 Detail s...
|
1792853633.5708451
|
1792940033.5708451
|
|
36820
|
🚀 Mission Control by @Harjinder | Stardance
|
Harjinder
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 🚀 Mission Control by @Harjinder | Stardance
|
1792515155.9782321
|
1793119955.9782321
|
|
28872
|
🚀 AstroBase by @dheerajtanaji | Stardance
|
dheerajtanaji
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 🚀 AstroBase by @dheerajtanaji | Stardance
|
1792756563.0441213
|
1793361363.0441213
|
|
19764
|
🕹️RASPICORE™ DECK by @Super_Gumka | Stardance
|
Super_Gumka
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 🕹️RASPICORE™ DECK by @Super_Gumka | Stardan Title: 🕹️RASPICORE™ DECK by @Super_Gumka | Stardance...
|
1792752506.528793
|
1793357306.528793
|
|
54059
|
📝 Project Introduction Title: Lunar Safe-Zone Navi 📝 Project Introduction Title: Lunar Safe-Zone Navigator — A Data-Based Decision System for Future Lunar Missions Introd by @sahilsonant2009 | Stardance...
|
sahilsonant2009
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 📝 Project Introduction Title: Lunar Safe-Zo Title: 📝 Project Introduction Title: Lunar Safe-Zone Navigator — A Data-Based Decision System for Future Lunar Missions Introd by @sahilsonant2009 | Stardance...
|
1792774325.3452759
|
1793379125.3452759
|
|
37511
|
🐞 Riddle-game🐈⬛ by @shra2408 | Stardance
|
shra2408
|
0
|
3.87
|
0
|
[]
|
[{"post_id": 46923, "ts": "202 [{"post_id": 46923, "ts": "2026-08-14T14:08:33Z", "hours": 0.8778, "text": "🐞Miraculous Ladybug & Cat noir Riddle-game🐈⬛ Devlog 5 The game where Marinette participates in a game where she joins this Paris-wide game challenge to save the celebrity “Adrien” by solving riddles, I want to replicate that game. I made a score system yay!"}, {"post_id": 46731, "ts": "2026-08-14T06:09:45Z", "hours": 0.8569, "text": "🐞Miraculous Ladybug & Cat noir Riddle-game🐈⬛ Devlog 4 The game where Marinette participates in a game where she joins this Paris-wide game challenge to save the celebrity “Adrien” by solving riddles, I want to replicate that game. I added a login function called Main()."}, {"post_id": 46117, "ts": "2026-08-13T03:57:47Z", "hours": 0.4581, "text": "🐞Miraculous Ladybug & Cat noir Riddle-game🐈⬛ Devlog 3 The game where Marinette participates in a game where she joins this Paris-wide game challenge to save the celebrity “Adrien” by solving riddles, I want to replicate that game. I added a class."}, {"post_id": 46113, "ts": "2026-08-13T03:24:33Z", "hours": 1.2825, "text": "🐞Miraculous Ladybug & Cat noir Riddle-game🐈⬛ Devlog 2 The game where Marinette participates in a game where she joins this Paris-wide game challenge to save the celebrity “Adrien” by solving riddles, I want to replicate that game. I made a names system."}, {"post_id": 45681, "ts": "2026-08-12T10:19:55Z", "hours": 0.3964, "text": "🐞Miraculous Ladybug & Cat noir Riddle-game🐈⬛ The game where Marinette participates in a game where she joins this Paris-wide game challenge to save the celebrity “Adrien” by solving riddles, I want to replicate that game."}]...
|
Title: 🐞 Riddle-game🐈⬛ by @shra2408 | Stardance
Title: 🐞 Riddle-game🐈⬛ by @shra2408 | Stardance
Devlogs:
🐞Miraculous Ladybug & Cat noir Riddle-game🐈⬛ The game where Marinette participates in a game where she joins this Paris-wide game challenge to save the celebrity “Adrien” by solving riddles, I want to replicate that game.
🐞Miraculous Ladybug & Cat noir Riddle-game🐈⬛ Devlog 2 The game where Marinette participates in a game where she joins this Paris-wide game challenge to save the celebrity “Adrien” by solving riddles, I want to replicate that game. I made a names system.
🐞Miraculous Ladybug & Cat noir Riddle-game🐈⬛ Devlog 3 The game where Marinette participates in a game where she joins this Paris-wide game challenge to save the celebrity “Adrien” by solving riddles, I want to replicate that game. I added a class.
🐞Miraculous Ladybug & Cat noir Riddle-game🐈⬛ Devlog 4 The game where Marinette participates in a game where she joins this Paris-wide game challenge to save the celebrity “Adrien” by solving riddles, I want to replicate that game. I added a login function called Main().
🐞Miraculous Ladybug & Cat noir Riddle-game🐈⬛ Devlog 5 The game where Marinette participates in a game where she joins this Paris-wide game challenge to save the celebrity “Adrien” by solving riddles, I want to replicate that game. I made a score system yay!...
|
1792745722.8695667
|
1793350522.8695667
|
|
17644
|
🐈Cat lover Slack bot by @mygulash | Stardance
|
mygulash
|
1
|
1.0
|
2
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-13T19:23:18Z", "hours": 1.0, "multiplier": 2.98, "payout": 2, "blessing": "neutral", "text": "My first ever project with Hack Club!✨ For my first project i chose creating a slack bot. My slack bot really really loves cats and it shows🐈He will gladly send you cat fun facts, images and even memes! After few hours of work i finally finished the code and could deploy it with nest so it runs 24/7. (The hackatime timer says it took me like 50 minutes even though i worked on it for like 4 hours… lol) For a beginner it was quite challenging to understand stuff like permissions and redirect URLs but Im happy to announce that its ready to ship! :D If you´re interested in this cat loving slack bot you can learn more about it in the read.me: https://github.com/Mygulash/LiborTheSlackBot/blob/main/README.md I hope that the cat memes, images and fun facts will make your day better :)🐈 Have a lovely day and pet your cat!✨", "repo": "https://github.com/Mygulash/LiborTheSlackBot", "demo": "https://hackclub.enterprise.slack.com/archives/C0B9Y31KHST"}]...
|
[{"post_id": 8060, "ts": "2026 [{"post_id": 8060, "ts": "2026-06-13T13:39:19Z", "hours": 0.7325, "text": "Finished the code for my Catloving Slack bot and now i´m waiting for my nest to get approved so i can host it ✨"}]...
|
Title: 🐈Cat lover Slack bot by @mygulash | Stardan Title: 🐈Cat lover Slack bot by @mygulash | Stardance
Devlogs:
Finished the code for my Catloving Slack bot and now i´m waiting for my nest to get approved so i can host it ✨
Ships:
My first ever project with Hack Club!✨ For my first project i chose creating a slack bot. My slack bot really really loves cats and it shows🐈He will gladly send you cat fun facts, images and even memes! After few hours of work i finally finished the code and could deploy it with nest so it runs 24/7. (The hackatime timer says it took me like 50 minutes even though i worked on it for like 4 hours… lol) For a beginner it was quite challenging to understand stuff like permissions and redirect URLs but Im happy to announce that its ready to ship! :D If you´re interested in this cat loving slack bot you can learn more about it in the read.me: https://github.com/Mygulash/LiborTheSlackBot/blob/main/README.md I hope that the cat memes, images and fun facts will make your day better :)🐈 Have a lovely day and pet your cat!✨...
|
1792810419.7140512
|
1792896819.7140512
|
|
1064
|
🌊Ocean pulse🐢 by @Fai | Stardance
|
Fai
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 🌊Ocean pulse🐢 by @Fai | Stardance
|
1792688025.506578
|
1793292825.506578
|
|
25936
|
𝑬𝒙𝒂𝒎-𝒊𝒏𝒂𝒕𝒐𝒓 by @Uncool | Stardance
|
Uncool
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 𝑬𝒙𝒂𝒎-𝒊𝒏𝒂𝒕𝒐𝒓 by @Uncool | Stardance
|
1791822187.7124093
|
1792686187.7124093
|
|
69249
|
𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫 𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫 by @inw | Stardance...
|
inw
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫 Title: 𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫𒐫 by @inw | Stardance...
|
1792475798.817386
|
1793080598.817386
|
|
34731
|
𐙚 dalias site ˖.𖥔 ݁ ⊹ ˖ 🏎 by @d_alsalim | Stardanc 𐙚 dalias site ˖.𖥔 ݁ ⊹ ˖ 🏎 by @d_alsalim | Stardance...
|
d_alsalim
|
1
|
6.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-19T23:26:47Z", "hours": 6.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "i made a personal website to showcase my own vibe and aesthetic while at the same time trying to refresh the things i learnt about html and css at school. for me it was challenging to keep the stickers in place as i had never worked with stickers before. im really proud of how aesthetically pleasing my website looks and how it really feels like my vibe esp with the apple music embed :)", "repo": "https://github.com/daliisalm22/dalias-personal-site", "demo": "https://daliisalm22.github.io/dalias-personal-site/"}]...
|
[{"post_id": 31503, "ts": "202 [{"post_id": 31503, "ts": "2026-07-19T23:16:45Z", "hours": 5.7219, "text": "after some long nights of coding that somehow still only added up to approximately like 6h on hackatime (im crineeee) I finally reached a point where I am kinda happy with my new personal website :) i really wanted to make this website cute and aesthetic and use it at the same time to showcase my own vibe and interests… ofc I struggled w/ some things esp the stickers were hard to keep in place but now that they really stick ig I can finally begin a new project haha so im shipping this site for now and I hope u guys like it <3 lmk what u think ^^"}, {"post_id": 28013, "ts": "2026-07-14T00:13:38Z", "hours": 0.6539, "text": "just started my first stardance project yayyyy"}]...
|
Title: 𐙚 dalias site ˖.𖥔 ݁ ⊹ ˖ 🏎 by @d_alsalim | S Title: 𐙚 dalias site ˖.𖥔 ݁ ⊹ ˖ 🏎 by @d_alsalim | Stardance
Devlogs:
just started my first stardance project yayyyy
after some long nights of coding that somehow still only added up to approximately like 6h on hackatime (im crineeee) I finally reached a point where I am kinda happy with my new personal website :) i really wanted to make this website cute and aesthetic and use it at the same time to showcase my own vibe and interests… ofc I struggled w/ some things esp the stickers were hard to keep in place but now that they really stick ig I can finally begin a new project haha so im shipping this site for now and I hope u guys like it <3 lmk what u think ^^
Ships:
i made a personal website to showcase my own vibe and aesthetic while at the same time trying to refresh the things i learnt about html and css at school. for me it was challenging to keep the stickers in place as i had never worked with stickers before. im really proud of how aesthetically pleasing my website looks and how it really feels like my vibe esp with the apple music embed :)...
|
1792849831.450752
|
1792936231.450752
|
|
45220
|
세티넽 by @karin | Stardance
|
karin
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 세티넽 by @karin | Stardance
|
1792615968.2831008
|
1793220768.2831008
|
|
9700
|
解任務 by @ElvisTang | Stardance
|
ElvisTang
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 解任務 by @ElvisTang | Stardance
|
1792677061.635055
|
1793281861.635055
|
|
63105
|
私は習近平が大好きです by @vexith | Stardance
|
vexith
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 私は習近平が大好きです by @vexith | Stardance
|
1792439556.668934
|
1793044356.668934
|
|
3140
|
禅文 Zenwen by @dylank | Stardance
|
dylank
|
1
|
21.0
|
243
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-03T00:49:03Z", "hours": 21.0, "multiplier": 11.65, "payout": 243, "blessing": "neutral", "text": "🏯 禅文 Zenwen Ship #1 Learning Chinese is hard, Zenwen makes it easier. Use the live page here: Zenwen Demo Bear in mind, it’s a demo, so no data is saved. As soon as you reload it’ll be lost. More info on running locally here: Main Repository What even is 禅文 Zenwen? Zenwen is an app to help you learn Chinese, and other languages if you wish. As of this ship, Zenwen is a vocab system designed to work for just about any need a user wants, while simple and easy to use. What was challenging First and foremost, learning Flutter was challenging. Dart is simple enough, but Flutter was something I had never seen before. The second challenge was figuring out an efficient data structure to store the many things users can create. This was challenging because I had to figure out how to store many decks with many vocab, while also being able to sort through them, search them, delete data, and access them quickly. Why I am proud! What makes me proud is that I learned an entire new framework and a lot about data storage that I had previously never touched. Learning this unlocks a whole world of coding opportunities that I’m excited to explore! Another thing I’m proud about is that I’ve learned how to debug better. I have learned how to use print functions usefully as well as things I previously didn’t know would cause errors.", "repo": "https://github.com/RandoWhoCodes/Zenwen/", "demo": "https://randowhocodes.github.io/Zenwen_Demo/"}]...
|
[{"post_id": 21193, "ts": "202 [{"post_id": 21193, "ts": "2026-07-03T00:20:20Z", "hours": 0.4414, "text": "🏯 禅文 Zenwen Day 11: SHIIIIIIIP!!!! Finally! Zenwen is shipped for the first time! (but expect lots more to come) Live demo here: Zenwen Demo , bear in mind all data is temporary and will be lost if you refresh. QoL Improvements Learning languages is no longer tedious. Handle everything you need in 1 place without complications. Supports every language! There are 3 things you can add when creating vocab: character, pronunciation, meaning. This means you could translate Egyptian hieroglyphics to Hindi as a French speaker if you really wanted to. Search for decks, and vocab! Forgot what deck some vocab is in, or just have way too many decks? No worries, just search for it! My Dictionary, all your vocab in 1 place! Simply want to see how much vocab you have or are just skimming through what you know? This is the perfect feature for you. 🐉 Chinese word of the day: 进步: progress, to make progress Pronounced: jìnbù Example: “我有了一点进步”, “I have made a little progress”"}, {"post_id": 20482, "ts": "2026-07-02T02:45:29Z", "hours": 0.7764, "text": "🏯 禅文 Zenwen Day 10: EVERYTHING WORKS!!! Finally! What I did during these 44 minutes Long story short, there was an indexing error when a search result wasn’t found. It was supposed to give a message like “no results matched your search”, but instead, it gave a big scary red screen saying “index is supposed to be less than 1: 1”. I had no clue what was wrong. Took a while to figure it out. Turns out I was stupid and trying to do widget.myDictionary.length when I was supposed to do widget.myDictionary[\"vocab\"].length . What’s coming next Ship! Everything is ready. Expect a ship tomorrow if I can set up the demo correctly! 🀄 Chinese word of the day Word: 买 Pronounced: mǎi Example: “我买了筷子。“ - “I bought chopsticks.”"}, {"post_id": 16117, "ts": "2026-06-26T06:28:13Z", "hours": 0.8953, "text": "🏯 Zenwen Day 9: everything works! Well, for now, at least. Overall, pretty quick and easy day. Simple bug fixes, simple feature expansions. What I did Fixed logic for when it was searching through My Dictionary for Strings that match the search Switched some 0s to 1s and stuff so it wouldn’t make duplicate search results or have indexing errors Added a search bar to the edit deck page so now you can search from every screen! What this means I’m almost ready to ship! Project works well enough to be tested, GitHub is up to date with commits. All I need to do is make the README and get a live web demo up and running! 🀄 Chinese word of the day 绿茶 (lǜ chá): Green Tea 我喜欢喝绿茶！ I like drinking green tea!"}, {"post_id": 13968, "ts": "2026-06-22T22:33:18Z", "hours": 2.3914, "text": "🏯 禅文 Zenwen Day 8, SEARCH BAR WORKS (mostly)!!!! Learning Chinese is hard. Zenwen makes it easier. Create infinite decks and vocab and find them easily! Apparently Expanded() widgets can only go in certain other widgets, so I was stuck solving bugs for nearly 45 minutes. Sometimes I question why I like coding. The logic for searching vocab is broken, but that was just me being dumb. Should be easy enough to fix. Will need to do heavy optimizing after I ship because I wrote it in probably the least efficient way possible, but it’s fine for now. Chinese word of the day: 飞机 (fēi jī) Means “airplane” ”这是飞机” = “this is an airplane”"}, {"post_id": 12895, "ts": "2026-06-21T03:44:53Z", "hours": 3.4953, "text": "🏯 禅文 Zenwen Day 6 & 7 (I swear that isn’t on purpose) TL;DR Finished My Dictionary; now there’s a master list of all your vocab! Great for if you want to see your progress or just forget a word. Starded working on a search bar! Worked on making my computer less laggy (no time logged for this) The Search Bar What’s the point in being able to make a bunch of decks and vocab if it takes too long to find them? Exactly, there is none. Today I started working on adding a search bar to the header of the app. Surprisingly, the logic behind it is pretty simple. Just iterate through the Maps and Lists . If an item matches your search, add it to a results Map . What I Learned You know those simple, boring headers at the top of basically every app? That’s what us Flutter devs call an AppBar . Apparently, AppBars have multiple parts: leading title (already knew about this one) trailing actions bottom The bottom is what I use for the search bar. Essentially, the bottom is an extension of widgets that are below the title. In order to make it work, you need to give the Scaffold (the parent of the AppBar ) specific details about the extension so that it renders properly. Specifically the height, which can’t be dynamic. 🀄 Since you made it this far Chinese word of the day: 吗 (pronounced “ma”) used to turn a statement into a yes or no question 你喜欢茶: You like tea. 你喜欢茶 吗 : Do you like tea?"}, {"post_id": 11430, "ts": "2026-06-18T18:14:30Z", "hours": 2.6472, "text": "🏯 禅文 Zenwen Day 5: documenting & my favorite feature! (and fixing 1028 issues with my computer) ⌚ TL;DR I added lots of comments to the code so that future me & other people can easily understand the code. Also started adding a cool feature called My Dictionary. 📝 Adding comments (finally) Wanna know something I never do? Add comments. Well at least not until today. Today I spent most of my time doing a well needed cleanup of the codebase, adding comments and making it readable to future me and other people. Since flutter can quickly start looking like a random jumble of widgets, adding these comments really helped me understand exactly what everything is doing and will help others understand as well. 📕 My Dictionary, my favorite feature! I also started working on adding a major QoL improvement, a deck that contains all the vocab you’ve created. Have you ever had a word on the tip of your tongue but just can’t quite remember it? That’s no longer a problem. With My Dictionary, you can open it up and quickly search up that word in just 3 clicks. You can also see how much vocab you have created, which feels amazing when you see how much you’ve learned! 🪲 1028 issues with my computer Don’t ask. I don’t have any answers for you. I checked Lenovo Vantage and now it finally makes sense why my computer struggled to run the file explorer. After a few hours of a well needed scan and fix by Lenovo Smart Performance, my computer now runs (mostly) smoothly once again."}, {"post_id": 10470, "ts": "2026-06-17T06:26:24Z", "hours": 2.2861, "text": "🏯 禅文 Zenwen - Devlog 4️⃣ 👋 你好！ Zenwen is an app to help people learn Chinese. As someone with a 970 day Duolingo streak, I know what us language learners need. ⌚ TL;DR HIT THE 10 HOUR MARK 🎉 Today I made the vocab page and made it so you can delete decks. I also polished up the graphics a bit. 📕 What I Learned Today I learned lots of useful things! I learned about some new styling for Material() widgets, along with 4 new widgets: Stack() IntrinsicHeight() Expanded() Padding() Also learned how to make if else statements in ListView.builders! 🗣️ In depth summary Today’s main objective was making the vocab page. To do this I used a simple ListView.builder to iterate through the vocab lists. One issue I had was the layout of the vocab. I wanted an equally spaced horizontal layout with a delete button floating at the right. This was a problem because I only knew about the Row() widget. In order to get the layout I wanted, I had to learn about Stack() and IntrinsicHeight() and Padding() and Expanded(). Another thing I ran into was that it crashed when I deleted all the decks or all the vocab. In order to fix this I learned about if else statements to create different widgets based on the conditions! 👣 Next Steps I’m almost ready to ship! I still have to make a few things though: a master vocab deck, and ideally a search bar. If the search bar goes well then I can also add filters for the decks if I decide it’s worth it."}, {"post_id": 9750, "ts": "2026-06-16T05:30:36Z", "hours": 2.9556, "text": "🏯 禅文 Zenwen - Devlog 3️⃣ 你好! Zenwen is an app to help people ACTUALLY learn languages. As someone with a 970 day Duolingo streak, I know what us learners need. The first thing I’m making for the app is vocab decks, and I’m almost ready to ship this! Today was focused on displaying the actual vocab in the decks as well as being able to add new vocab. Learned a lot about how to handle inputs in Flutter. This morning I realized my button layout wasn’t very convenient for users, so I had to rearrange it, which forced me to learn about InkWell, which will help me learn a lot moving forward."}, {"post_id": 9005, "ts": "2026-06-15T00:43:06Z", "hours": 1.8233, "text": "🏯 禅文 Zenwen - Devlog 2️⃣ 你好！ Zenwen is an app I’m making with Flutter to help people ACRUALLY learn languages. As someone with a 970 day Duolingo streak, I know what us language learners need to actually be successful. Made a lot of progress today! I developed a basic display of vocab decks, which includes: title, description, practice button, edit button. Also made a way to create new vocab decks, by clicking the button at the bottom right. You can’t view or add vocab yet, that’s hopefully coming tomorrow. The UI is pretty bare bones right now. I’m focused on functionality before I make it look good. As for bugs I encountered, the entire app crashed when I switched from using a stateless widget to a stateful widget. Quickly discovered this was me being stupid because I forgot to restart the app. Apparently hot reload doesn’t like big changes between stateless and stateful."}, {"post_id": 8526, "ts": "2026-06-14T05:35:36Z", "hours": 3.3131, "text": "🏯 禅文 Zenwen - Devlog 1️⃣ Zenwen is (will be) an app to help people ACTUALLY learn languages like Chinese. As someone with a 960 day Duolingo streak, I know exactly what us language learners need. My first ship will be a tool for making and studying vocab decks to seamlessly fit in with your day. Today was a short but productive. The app is basically just a blank screen on the front end, but the systems are falling into place in the code. Today I developed the system for storing vocab decks. Now it should be fairly easy to add flashcards and other study tools. The first hour or so of the day was spent fixing VSCode because lots of things were breaking. It said my phone was connected, but it wouldn’t show up. The Flutter extension also stopped working. Changed the name from Zhenwen to Zenwen. Zhenwen has religious cultural meanings, so I want to respect that. 真文 means “true text”, which has meanings in Taoism. 禅文 (technically chánwén) essentially means “peaceful language”. For your entertainment here is a screenshot of a stupid bug that confused me for 30 minutes. 99k pixel overflow. Can’t wait to see what the next week will bring and watch this app come to life!"}]...
|
Title: 禅文 Zenwen by @dylank | Stardance
Devlogs:
Title: 禅文 Zenwen by @dylank | Stardance
Devlogs:
🏯 禅文 Zenwen - Devlog 1️⃣ Zenwen is (will be) an app to help people ACTUALLY learn languages like Chinese. As someone with a 960 day Duolingo streak, I know exactly what us language learners need. My first ship will be a tool for making and studying vocab decks to seamlessly fit in with your day. Today was a short but productive. The app is basically just a blank screen on the front end, but the systems are falling into place in the code. Today I developed the system for storing vocab decks. Now it should be fairly easy to add flashcards and other study tools. The first hour or so of the day was spent fixing VSCode because lots of things were breaking. It said my phone was connected, but it wouldn’t show up. The Flutter extension also stopped working. Changed the name from Zhenwen to Zenwen. Zhenwen has religious cultural meanings, so I want to respect that. 真文 means “true text”, which has meanings in Taoism. 禅文 (technically chánwén) essentially means “peaceful language”. For your entertainment here is a screenshot of a stupid bug that confused me for 30 minutes. 99k pixel overflow. Can’t wait to see what the next week will bring and watch this app come to life!
🏯 禅文 Zenwen - Devlog 2️⃣ 你好！ Zenwen is an app I’m making with Flutter to help people ACRUALLY learn languages. As someone with a 970 day Duolingo streak, I know what us language learners need to actually be successful. Made a lot of progress today! I developed a basic display of vocab decks, which includes: title, description, practice button, edit button. Also made a way to create new vocab decks, by clicking the button at the bottom right. You can’t view or add vocab yet, that’s hopefully coming tomorrow. The UI is pretty bare bones right now. I’m focused on functionality before I make it look good. As for bugs I encountered, the entire app crashed when I switched from using a stateless widget to a stateful widget. Quickly discovered this was me being stupid because I forgot to restart the app. Apparently hot reload doesn’t like big changes between stateless and stateful.
🏯 禅文 Zenwen - Devlog 3️⃣ 你好! Zenwen is an app to help people ACTUALLY learn languages. As someone with a 970 day Duolingo streak, I know what us learners need. The first thing I’m making for the app is vocab decks, and I’m almost ready to ship this! Today was focused on displaying the actual vocab in the decks as well as being able to add new vocab. Learned a lot about how to handle inputs in Flutter. This morning I realized my button layout wasn’t very convenient for users, so I had to rearrange it, which forced me to learn about InkWell, which will help me learn a lot moving forward.
🏯 禅文 Zenwen - Devlog 4️⃣ 👋 你好！ Zenwen is an app to help people learn Chinese. As someone with a 970 day Duolingo streak, I know what us language learners need. ⌚ TL;DR HIT THE 10 HOUR MARK 🎉 Today I made the vocab page and made it so you can delete decks. I also polished up the graphics a bit. 📕 What I Learned Today I learned lots of useful things! I learned about some new styling for Material() widgets, along with 4 new widgets: Stack() IntrinsicHeight() Expanded() Padding() Also learned how to make if else statements in ListView.builders! 🗣️ In depth summary Today’s main objective was making the vocab page. To do this I used a simple ListView.builder to iterate through the vocab lists. One issue I had was the layout of the vocab. I wanted an equally spaced horizontal layout with a delete button floating at the right. This was a problem because I only knew about the Row() widget. In order to get the layout I wanted, I had to learn about Stack() and IntrinsicHeight() and Padding() and Expanded(). Another thing I ran into was that it crashed when I deleted all the decks or all the vocab. In order to fix this I learned about if else statements to create different widgets based on the conditions! 👣 Next Steps I’m almost ready to ship! I still have to make a few things though: a master vocab deck, and ideally a search bar. If the search bar goes well then I can also add filters for the decks if I decide it’s worth it.
🏯 禅文 Zenwen Day 5: documenting & my favorite feature! (and fixing 1028 issues with my computer) ⌚ TL;DR I added lots of comments to the code so that future me & other people can easily understand the code. Also started adding a cool feature called My Dictionary. 📝 Adding comments (finally) Wanna know something I never do? Add comments. Well at least not until today. Today I spent most of my time doing a well needed cleanup of the codebase, adding comments and making it readable to future me and other people. Since flutter can quickly start looking like a random jumble of widgets, adding these comments really helped me understand exactly what everything is doing and will help others understand as well. 📕 My Dictionary, my favorite feature! I also started working on adding a major QoL improvement, a deck that contains all the vocab you’ve created. Have you ever had a word on the tip of your tongue but just can’t quite remember it? That’s no longer a problem. With My Dictionary, you can open it up and quickly search up that word in just 3 clicks. You can also see how much vocab you have created, which feels amazing when you see how much you’ve learned! 🪲 1028 issues with my computer Don’t ask. I don’t have any answers for you. I checked Lenovo Vantage and now it finally makes sense why my computer struggled to run the file explorer. After a few hours of a well needed scan and fix by Lenovo Smart Performance, my computer now runs (mostly) smoothly once again.
🏯 禅文 Zenwen Day 6 & 7 (I swear that isn’t on purpose) TL;DR Finished My Dictionary; now there’s a master list of all your vocab! Great for if you want to see your progress or just forget a word. Starded working on a search bar! Worked on making my computer less laggy (no time logged for this) The Search Bar What’s the point in being able to make a bunch of decks and vocab if it takes too long to find them? Exactly, there is none. Today I started working on adding a search bar to the header of the app. Surprisingly, the logic behind it is pretty simple. Just iterate through the Maps and Lists . If an item matches your search, add it to a results Map . What I Learned You know those simple, boring headers at the top of basically every app? That’s what us Flutter devs call an AppBar . Apparently, AppBars have multiple parts: leading title (already knew about this one) trailing actions bottom The bottom is what I use for the search bar. Essentially, the bottom is an extension of widgets that are below the title. In order to make it work, you need to give the Scaffold (the parent of the AppBar ) specific details about the extension so that it renders properly. Specifically the height, which can’t be dynamic. 🀄 Since you made it this far Chinese word of the day: 吗 (pronounced “ma”) used to turn a statement into a yes or no question 你喜欢茶: You like tea. 你喜欢茶 吗 : Do you like tea?
🏯 禅文 Zenwen Day 8, SEARCH BAR WORKS (mostly)!!!! Learning Chinese is hard. Zenwen makes it easier. Create infinite decks and vocab and find them easily! Apparently Expanded() widgets can only go in certain other widgets, so I was stuck solving bugs for nearly 45 minutes. Sometimes I question why I like coding. The logic for searching vocab is broken, but that was just me being dumb. Should be easy enough to fix. Will need to do heavy optimizing after I ship because I wrote it in probably the least efficient way possible, but it’s fine for now. Chinese word of the day: 飞机 (fēi jī) Means “airplane” ”这是飞机” = “this is an airplane”
🏯 Zenwen Day 9: everything works! Well, for now, at least. Overall, pretty quick and easy day. Simple bug fixes, simple feature expansions. What I did Fixed logic for when it was searching through My Dictionary for Strings that match the search Switched some 0s to 1s and stuff so it wouldn’t make duplicate search results or have indexing errors Added a search bar to the edit deck page so now you can search from every screen! What this means I’m almost ready to ship! Project works well enough to be tested, GitHub is up to date with commits. All I need to do is make the README and get a live web demo up and running! 🀄 Chinese word of the day 绿茶 (lǜ chá): Green Tea 我喜欢喝绿茶！ I like drinking green tea!
🏯 禅文 Zenwen Day 10: EVERYTHING WORKS!!! Finally! What I did during these 44 minutes Long story short, there was an indexing error when a search result wasn’t found. It was supposed to give a message like “no results matched your search”, but instead, it gave a big scary red screen saying “index is supposed to be less than 1: 1”. I had no clue what was wrong. Took a while to figure it out. Turns out I was stupid and trying to do widget.myDictionary.length when I was supposed to do widget.myDictionary["vocab"].length . What’s coming next Ship! Everything is ready. Expect a ship tomorrow if I can set up the demo correctly! 🀄 Chinese word of the day Word: 买 Pronounced: mǎi Example: “我买了筷子。“ - “I bought chopsticks.”
🏯 禅文 Zenwen Day 11: SHIIIIIIIP!!!! Finally! Zenwen is shipped for the first time! (but expect lots more to come) Live demo here: Zenwen Demo , bear in mind all data is temporary and will be lost if you refresh. QoL Improvements Learning languages is no longer tedious. Handle everything you need in 1 place without complications. Supports every language! There are 3 things you can add when creating vocab: character, pronunciation, meaning. This means you could translate Egyptian hieroglyphics to Hindi as a French speaker if you really wanted to. Search for decks, and vocab! Forgot what deck some vocab is in, or just have way too many decks? No worries, just search for it! My Dictionary, all your vocab in 1 place! Simply want to see how much vocab you have or are just skimming through what you know? This is the perfect feature for you. 🐉 Chinese word of the day: 进步: progress, to make progress Pronounced: jìnbù Example: “我有了一点进步”, “I have made a little progress”
Ships:
🏯 禅文 Zenwen Ship #1 Learning Chinese is hard, Zenwen makes it easier. Use the live page here: Zenwen Demo Bear in mind, it’s a demo, so no data is saved. As soon as you reload it’ll be lost. More info on running locally here: Main Repository What even is 禅文 Zenwen? Zenwen is an app to help you learn Chinese, and other languages if you wish. As of this ship, Zenwen is a vocab system designed to work for just about any need a user wants, while simple and easy to use. What was challenging First and foremost, learning Flutter was challenging. Dart is simple enough, but Flutter was something I had never seen before. The second challenge was figuring out an efficient data structure to store the many things users can create. This was challenging because I had to figure out how to store many decks with many vocab, while also being able to sort through them, search them, delete data, and access them quickly. Why I am proud! What makes me proud is that I learned an entire new framework and a lot about data storage that I had previously never touched. Learning this unlocks a whole world of coding opportunities that I’m excited to explore! Another thing I’m proud about is that I’ve learned how to debug better. I have learned how to use print functions usefully as well as things I previously didn’t know would cause errors....
|
1792835605.3240247
|
1792922005.3240247
|
|
70610
|
电热膜恒温手套 by @LuLing | Stardance
|
LuLing
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 电热膜恒温手套 by @LuLing | Stardance
|
1792493247.5908377
|
1793098047.5908377
|
|
61358
|
栖苞 by @2295905258 | Stardance
|
2295905258
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 栖苞 by @2295905258 | Stardance
|
1792432106.906912
|
1793036906.906912
|
|
10502
|
星球大战 by @bugjiang | Stardance
|
bugjiang
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 星球大战 by @bugjiang | Stardance
|
1792669645.5721233
|
1793274445.5721233
|
|
66048
|
改善(Kaizen) by @MAyaanBaig2013 | Stardance
|
MAyaanBaig2013
|
1
|
1.0
|
1
|
[{"ship_num": 1, "ts": "2026-1 [{"ship_num": 1, "ts": "2026-10-03T15:07:54Z", "hours": 1.0, "multiplier": 1.01, "payout": 1, "blessing": "neutral", "text": "I made an goal tracker using AI for the buttons and notes.The challanging part was of the code", "repo": "https://github.com/DevAyaan123/Kaizen", "demo": "https://devayaan123.github.io/Kaizen/"}]...
|
[{"post_id": 76423, "ts": "202 [{"post_id": 76423, "ts": "2026-10-03T14:16:09Z", "hours": 0.4511, "text": "After some lot of struggling and coding I finally broke through"}, {"post_id": 75888, "ts": "2026-10-01T14:40:52Z", "hours": 0.7669, "text": "devlog 1 Hey Guys,NEW project here ,After a lot of coding with the help of AI for styling,pading and the note I made this!!"}]...
|
Title: 改善(Kaizen) by @MAyaanBaig2013 | Stardance
Title: 改善(Kaizen) by @MAyaanBaig2013 | Stardance
Devlogs:
devlog 1 Hey Guys,NEW project here ,After a lot of coding with the help of AI for styling,pading and the note I made this!!
After some lot of struggling and coding I finally broke through
Ships:
I made an goal tracker using AI for the buttons and notes.The challanging part was of the code...
|
1792817298.522452
|
1792903698.522452
|
|
46794
|
小さなロボット by @maindanikraft | Stardance
|
maindanikraft
|
0
|
5.27
|
0
|
[]
|
[{"post_id": 48579, "ts": "202 [{"post_id": 48579, "ts": "2026-08-17T01:07:37Z", "hours": 0.5667, "text": "DevLog 4 I was working on some design for a firmer moving base and a way I can fix the problem of the support main base for the arm is moving up and down and not flat."}, {"post_id": 46440, "ts": "2026-08-13T17:30:00Z", "hours": 1.2736, "text": "Robot Arm Base DevLog #3 Basically, I simply built a moving arm, found the motor stl, fixed gears underneath, and fixed the size of the temporary screw sets. I will then work on the gear boxes and motors to make this work."}, {"post_id": 45400, "ts": "2026-08-11T20:33:01Z", "hours": 3.4336, "text": "DEVLOG #1 I was mostly learning new stuff than actually building. I was able to finish the base and basic gear move for a step motor. I will work on the arm itself next and find specific stls of pieces."}]...
|
Title: 小さなロボット by @maindanikraft | Stardance
Devl Title: 小さなロボット by @maindanikraft | Stardance
Devlogs:
DEVLOG #1 I was mostly learning new stuff than actually building. I was able to finish the base and basic gear move for a step motor. I will work on the arm itself next and find specific stls of pieces.
Robot Arm Base DevLog #3 Basically, I simply built a moving arm, found the motor stl, fixed gears underneath, and fixed the size of the temporary screw sets. I will then work on the gear boxes and motors to make this work.
DevLog 4 I was working on some design for a firmer moving base and a way I can fix the problem of the support main base for the arm is moving up and down and not flat....
|
1792486518.8336036
|
1793091318.8336036
|
|
12081
|
吃音の特徴を自己理解する by @go10mitsuki | Stardance
|
go10mitsuki
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 吃音の特徴を自己理解する by @go10mitsuki | Stardance
|
1792569047.7858176
|
1793173847.7858176
|
|
61956
|
三 swap by @hoshi | Stardance
|
hoshi
|
1
|
4.0
|
47
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-15T03:33:23Z", "hours": 4.0, "multiplier": 11.28, "payout": 47, "blessing": "neutral", "text": "ARROW KEYS TO MOVE! this small game generates a random 10 by 10 board that consists of colors WHITE, BLACK, and GOLD. You are a player starting from the left corner. Every tile you step on, the tile changes color.", "repo": "https://github.com/uuukye/san_swap", "demo": "https://uuukye.github.io/san_swap/"}]...
|
[{"post_id": 68429, "ts": "202 [{"post_id": 68429, "ts": "2026-09-15T03:15:34Z", "hours": 2.0692, "text": "DEVLOG #2 ______________________________________________________________________________________ Since it was really complicated setting up a live server with leaderboard, and people may cheat, I chose not to include the leaderboard. I think the game is good as it-is. I was supposed to be a small game anyway I made the game structure way better so the game would not lag (hopefully), and I added a timer function. ______________________________________________________________________________________ I tested this game a couple of times and I got an average time of 35 seconds :D tell me what time you got!"}, {"post_id": 67758, "ts": "2026-09-14T00:13:39Z", "hours": 2.0778, "text": "DEVLOG #1 ______________________________________________________________________________________ So basically, this small game generates a random 10 by 10 board that consists of colors WHITE , BLACK , and GOLD . You are a player starting from the left corner. Every tile you step on, the tile changes color. ______________________________________________________________________________________ 1) If a tile was WHITE , it will turn GOLD . ______________________________________________________________________________________ 2) If the tile was GOLD , it will turn BLACK . ______________________________________________________________________________________ 3) If the tile was BLACK , it will turn WHITE . ______________________________________________________________________________________ The goal of this game is to make the whole board the same color . ______________________________________________________________________________________ Basically, I made the whole game physics and the timer. If I can understand global servers better, I might add a leaderboard. I am also planning to update the character’s appearance because right now it’s just a circle. I was inspired by the “Lights Out” mathematical game. ______________________________________________________________________________________ What made me take so much time was making the board, because if I do not set any constraints, there is only a one-third chance of the board being possible to solve. So I did some math, and I somehow made it so it’s hopefully possible on all generated positions."}]...
|
Title: 三 swap by @hoshi | Stardance
Devlogs:
DEVL Title: 三 swap by @hoshi | Stardance
Devlogs:
DEVLOG #1 ______________________________________________________________________________________ So basically, this small game generates a random 10 by 10 board that consists of colors WHITE , BLACK , and GOLD . You are a player starting from the left corner. Every tile you step on, the tile changes color. ______________________________________________________________________________________ 1) If a tile was WHITE , it will turn GOLD . ______________________________________________________________________________________ 2) If the tile was GOLD , it will turn BLACK . ______________________________________________________________________________________ 3) If the tile was BLACK , it will turn WHITE . ______________________________________________________________________________________ The goal of this game is to make the whole board the same color . ______________________________________________________________________________________ Basically, I made the whole game physics and the timer. If I can understand global servers better, I might add a leaderboard. I am also planning to update the character’s appearance because right now it’s just a circle. I was inspired by the “Lights Out” mathematical game. ______________________________________________________________________________________ What made me take so much time was making the board, because if I do not set any constraints, there is only a one-third chance of the board being possible to solve. So I did some math, and I somehow made it so it’s hopefully possible on all generated positions.
DEVLOG #2 ______________________________________________________________________________________ Since it was really complicated setting up a live server with leaderboard, and people may cheat, I chose not to include the leaderboard. I think the game is good as it-is. I was supposed to be a small game anyway I made the game structure way better so the game would not lag (hopefully), and I added a timer function. ______________________________________________________________________________________ I tested this game a couple of times and I got an average time of 35 seconds :D tell me what time you got!
Ships:
ARROW KEYS TO MOVE! this small game generates a random 10 by 10 board that consists of colors WHITE, BLACK, and GOLD. You are a player starting from the left corner. Every tile you step on, the tile changes color....
|
1792813902.293876
|
1792900302.293876
|
|
70294
|
この世界への不満を訴えるボカロ by @oninihottodoggu | Stardance
|
oninihottodoggu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: この世界への不満を訴えるボカロ by @oninihottodoggu | Stard Title: この世界への不満を訴えるボカロ by @oninihottodoggu | Stardance...
|
1792320428.3490427
|
1792925228.3490427
|
|
9102
|
【Once Upon a Tale】 by @kxie | Stardance
|
kxie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 【Once Upon a Tale】 by @kxie | Stardance
|
1792565649.5366945
|
1793170449.5366945
|
|
12531
|
⭐Hackpad⭐ by @Tentem | Stardance
|
Tentem
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ⭐Hackpad⭐ by @Tentem | Stardance
|
1792536483.5298195
|
1793141283.5298195
|
|
415
|
⠀⠀ by @X | Stardance
|
X
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ⠀⠀ by @X | Stardance
|
1792594300.8870513
|
1793199100.8870513
|
|
16102
|
⠀ by @X | Stardance
|
X
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ⠀ by @X | Stardance
|
1792478957.0310137
|
1793083757.0310137
|
|
16104
|
⠀ by @X | Stardance
|
X
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ⠀ by @X | Stardance
|
1792482637.422925
|
1793087437.422925
|
|
68656
|
❄️ The Last Snowflake by @nour0hony | Stardance
|
nour0hony
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ❄️ The Last Snowflake by @nour0hony | Stard Title: ❄️ The Last Snowflake by @nour0hony | Stardance...
|
1792472051.1180704
|
1793076851.1180704
|
|
39677
|
✨ amazing amd bc-250 case✨ by @weltrinox | Stardan ✨ amazing amd bc-250 case✨ by @weltrinox | Stardance...
|
weltrinox
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ✨ amazing amd bc-250 case✨ by @weltrinox | Title: ✨ amazing amd bc-250 case✨ by @weltrinox | Stardance...
|
1791822611.4648967
|
1792686611.4648967
|
|
52208
|
✨ Cosmic Atlas by @__Sohaa__ | Stardance
|
__Sohaa__
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ✨ Cosmic Atlas by @__Sohaa__ | Stardance
|
1792702096.8868072
|
1793306896.8868072
|
|
3167
|
☆ magic drumsticks ☆ by @chelle | Stardance
|
chelle
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ☆ magic drumsticks ☆ by @chelle | Stardance
|
1792569068.9198213
|
1793173868.9198213
|
|
69331
|
★-My portfolie-but make it better and underwater - ★-My portfolie-but make it better and underwater -★ by @253_Mathilde_IYKYK | Stardance...
|
253_Mathilde_IYKYK
|
0
|
11.54
|
0
|
[]
|
[{"post_id": 79989, "ts": "202 [{"post_id": 79989, "ts": "2026-10-15T19:24:52Z", "hours": 2.5886, "text": "So what did I do today: For you I did norhing but for me I worked my life through responsive tutorials and started making the site responsive. Because this is my portfolio and it has to work on phones or laptops/tablets too. My plan is to only build the deskop site for now ship then the phone ship and then the tablet/laptop. For the phone version there will be somehting to move around the submarine I believe. Thanks for reading and thanks @matthewwong12 for your help <3"}, {"post_id": 79639, "ts": "2026-10-14T19:59:03Z", "hours": 2.0053, "text": "And another update for today: Fullscreen should work now. It would really help if you tried it out (go to the site and then F11 on windows ,idk apple) and tell me if everything looks right. This was pretty complicated for me but at least I figured a way out. Thanks for reading and your help <3 and here is the link: https://253-mathilde.github.io/My-portfolio/"}, {"post_id": 79546, "ts": "2026-10-14T15:25:26Z", "hours": 4.0094, "text": "That escalated quickly. Really really quickly. The music player is soooooooo good. I cannot be calm about this I am sorry. Look at all the fishes and uhh the light feature works with a flashlight or the key l or L now. The font has changed,it also got an hover effect the background music get’s you so in the zone and just imagine how I’ll build so much stuff into this. I am sooo happy and yes yes Ik I normally log every 2 hours but I coded in school and couldn’t write one and I was so in the work thingy that I couded 2 more hours at home. What do you think about the cursor? I made it myself and added that bubble effect that follows the submarine. Thanks for reading <3"}, {"post_id": 79386, "ts": "2026-10-13T19:23:20Z", "hours": 0.8442, "text": "As you can see, I added this super cool new feature: the dark mode. As I love dark modes, they are kind of boring on sites because they always look the same and often aren’t really designed (they just make EVERYTHING black -no, I don’t want to look at a black wall), so I added a cooler way for my site. It is currently working with an and not an but I’ll change that tomorrow as well as the cursor because the current cursor does look good but is super bad to use. Thanks for reading <3 SR FOR THE VD I REALLY NEED AN UPGRADE FOR THAT"}, {"post_id": 79067, "ts": "2026-10-12T15:43:05Z", "hours": 2.0939, "text": "I decided to start working on my next project while waiting for the other one to get accepted (from Google). This project will be an upgraded version of my personal site. I want to build something like an underwater city with houses, and each house holds information, so for example, you click on the telephone cell to get to an under site which shows my contact information, etc. I just worked on the graphics and stuff a little, and I kind of missed that. Do not get me wrong, I love my other project, but this is just so relaxing and calming at the moment. This site will also have a dark mode where your cursor turns into a flashlight, btw. What do we think about this idea? Thanks for reading <3"}]...
|
Title: ★-My portfolie-but make it better and under Title: ★-My portfolie-but make it better and underwater -★ by @253_Mathilde_IYKYK | Stardance
Devlogs:
I decided to start working on my next project while waiting for the other one to get accepted (from Google). This project will be an upgraded version of my personal site. I want to build something like an underwater city with houses, and each house holds information, so for example, you click on the telephone cell to get to an under site which shows my contact information, etc. I just worked on the graphics and stuff a little, and I kind of missed that. Do not get me wrong, I love my other project, but this is just so relaxing and calming at the moment. This site will also have a dark mode where your cursor turns into a flashlight, btw. What do we think about this idea? Thanks for reading <3
As you can see, I added this super cool new feature: the dark mode. As I love dark modes, they are kind of boring on sites because they always look the same and often aren’t really designed (they just make EVERYTHING black -no, I don’t want to look at a black wall), so I added a cooler way for my site. It is currently working with an and not an but I’ll change that tomorrow as well as the cursor because the current cursor does look good but is super bad to use. Thanks for reading <3 SR FOR THE VD I REALLY NEED AN UPGRADE FOR THAT
That escalated quickly. Really really quickly. The music player is soooooooo good. I cannot be calm about this I am sorry. Look at all the fishes and uhh the light feature works with a flashlight or the key l or L now. The font has changed,it also got an hover effect the background music get’s you so in the zone and just imagine how I’ll build so much stuff into this. I am sooo happy and yes yes Ik I normally log every 2 hours but I coded in school and couldn’t write one and I was so in the work thingy that I couded 2 more hours at home. What do you think about the cursor? I made it myself and added that bubble effect that follows the submarine. Thanks for reading <3
And another update for today: Fullscreen should work now. It would really help if you tried it out (go to the site and then F11 on windows ,idk apple) and tell me if everything looks right. This was pretty complicated for me but at least I figured a way out. Thanks for reading and your help <3 and here is the link: https://253-mathilde.github.io/My-portfolio/
So what did I do today: For you I did norhing but for me I worked my life through responsive tutorials and started making the site responsive. Because this is my portfolio and it has to work on phones or laptops/tablets too. My plan is to only build the deskop site for now ship then the phone ship and then the tablet/laptop. For the phone version there will be somehting to move around the submarine I believe. Thanks for reading and thanks @matthewwong12 for your help <3...
|
1792475884.056333
|
1793080684.056333
|
|
30331
|
∇Calc by @EngThi | Stardance
|
EngThi
|
0
|
64.45
|
0
|
[]
|
[{"post_id": 79791, "ts": "202 [{"post_id": 79791, "ts": "2026-10-15T12:42:36Z", "hours": 0.5311, "text": "I just finished redoing the parts of the case the parts there and everything else in the project after this second round. This last one that was missing was from Part Studio 4 , which was the little slider drawer for camera privacy and protection on the back 🔒 , along with Part Studio 5 where I made the sliding lid/cover. Very, very simple. I also added some small slots there just to give it a nice tactile texture/grip — pretty small, with a 0.350 mm cut extrusion (removing material). That was kind of the piece I was still missing. It was simple and quick since I already had the basic idea from earlier attempts. Oh, and one thing I think I forgot to mention before: I imported .DXF files into the sketch to help guide the drawings, basically defining the extrusions for the parts. It turned out pretty good! To wrap up, I added what I had forgotten before: the mounting holes on the back cover bosses. Put 1.6mm holes there to hold the screws properly ⚙️ ."}, {"post_id": 79509, "ts": "2026-10-14T11:14:33Z", "hours": 1.2011, "text": "For now I’m working on the CAD ; I had finished the PCB. I put up a quick video of how it turned out I recorded it with Canva, which I’d used before for a school project, and it works. I even have the Spectacle app for Linux , but it records in 720p, which looks kind of bad, so recording it online through Canva ends up looking way better. Basically, it has the dimensions of part two , which I was rethinking and everything. And well, this was more or less the idea I had: there’s the front part for the buttons, and in this other version, it was supposed to have a passage for a circuit board to fit a small solar cell ☀️ . Depending on what I can find around the house and if there’s any leftover space in the casing (it’s pretty much ready), I might implement it even if it ends up mounted on the outside rather than inside the case, just for reuse and photovoltaic charging. Then I also put the back part together: the little hole for the camera 📷 , the slider for its protection, and on the side, the microSD card slot. The keymat for the buttons which I changed the layout of, so it’s not square anymore now has roughly the positions for all 49 keys and the holes where the support bosses will go. There’s also that little strip/rectangle, which is meant to be the protective cover fitting right into the other slot. Basically, that’s it! I’ll continue and tweak it later. It’s not too difficult, and I think it’ll be finished soon."}, {"post_id": 77958, "ts": "2026-10-08T23:51:34Z", "hours": 0.9608, "text": "It’s kind of funny that I messed with this again, but basically this is a version where I repositioned the buttons and pins because, well, I decided the keys aren’t going to stay as a plain square matrix. So I kind of organized and divided things there to get a better idea of how the pins will be placed roughly around the center. On the top part, there’s sort of that D-pad area (not an actual single pad, but the individual buttons for that navigation). That circular button style you see on game controllers, handhelds , and on some other calculators too. I also moved the FPC connector over to the corner so it’s way easier and cleaner to connect everything up . On top of that, I rounded the board edges in this version. Overall, that was pretty much it! Lapse: Lapse"}, {"post_id": 77073, "ts": "2026-10-05T15:33:01Z", "hours": 0.7336, "text": "Keypad PCB done! Top & Bottom preview Now that I’ve finished, I’ve completed the PCB both images, the top and the bottom . I left the spaces for the M2 screws and already rotated everything, it was pretty easy! Basically, I kind of left an array, a 7x7 matrix . The keys would be more or less standardized and the only difference would be in the pad — like, in the rubber, the material that you press to trigger that key. That kind of thing. It turned out pretty nice. It’s simple, it’s actually simple to do this part, this kind of thing… That’s how it turned out. I’m not sure if I’ll tweak it much to add things like a D-pad or other types of keys for navigation, functions, the numeric keypad itself , that kind of stuff."}, {"post_id": 77024, "ts": "2026-10-05T12:20:38Z", "hours": 1.9592, "text": "I’m back! Finalized the second PCB for the keys Well, yeah, I’m here again. I’m back, it’s been a while since I was away, right? I waited for things to settle down here so I could continue with the project. Yeah, and I finalized the idea of making a board on the second PCB there, where the buttons will be, you know, the clicks to use the calculator keys . And this here was kind of leftover code organization I was doing in the repository . I ended up not remembering everything from the project, but now I’m here again. So I’ll finish this up. It was pretty simple, I didn’t record it. But basically, I made a 7x7 matrix of switches , the buttons. Along with that, there’s the FPC connector to actually connect the board to the ribbon, to the rest of the MCP expander. I’m going to tidy it up a bit. The board also ended up being quite small 84x78 basically just to fit there, it would provide support and, you know, fit the switches at the distances that had already been predetermined in the case , right in the middle of the product’s housing. And then, along with that, the schematic is also simple, I just put an FPC connector , that’s all that’s really needed, and the buttons, the switches. Really simple. I think it’s interesting to mention (diodes & debounce): I was also going to use, you know, I was looking, people were saying, it’s good to use diodes , but just to kind of reduce debounce , fix certain issues, but it wouldn’t be that necessary, since the contacts closing would almost never happen like, I don’t know, three clicks at once, one next to the other. So that doesn’t really cause a problem where the ESP wouldn’t know exactly which key is being pressed and what it should do with the signal it’s receiving. And depending on how you study it and see how to handle it in the firmware , it actually wouldn’t even be that necessary to put these diodes on each of these buttons for that."}, {"post_id": 58915, "ts": "2026-08-31T14:11:46Z", "hours": 1.8789, "text": "almost ready to submit!!! Finished and I’m getting ready to submit the project for review! I took some new renders and also did the prices part for the project items. I have everything here now and it is looking nice. Like I said before, I left some points to see and change better on the case when I have everything in my hands, so I can prototype 🤖 it better. I don’t have much skill with soldering, so I really hope I can get the Top PCBA . This is all really cool and interesting that I was able to do, and I’m really happy about it. At the end I also organized things a little more and changed stuff to track what is needed in the repo , help anyone that wants to look at it or reproduce the project somehow. The System architecture section got really cool in the translation and organization, AI did that . I don’t really know how to make this type of diagram myself yet :/ I hope I didn’t forget anything and that the organization I made, and later asked to improve, documents the state well. Basically I: I finished organizing the repo, checking the prices, calculations , etc., taking screenshots , I kept iterating in the repo, editing, moving things , that kind of organization 🗂️"}, {"post_id": 58142, "ts": "2026-08-30T14:30:08Z", "hours": 0.6419, "text": "more docs things right these Well, I tidied up the README and organized the folders and file names better. The repo in general . The other image is because I think I didn’t show it properly here and I was reposting , checking items and analyzing anything left there on EasyEDA"}, {"post_id": 57737, "ts": "2026-08-30T00:16:59Z", "hours": 1.2197, "text": "its possible only four images… I fiddled a bit more with these items, files 📁 , repo organization , stuff like that . Also, I took screenshots of some views from the project’s mechanical render … I’m not really focusing on any one part, but I tinker a bit here and if I remember something I should have done or think could be better, I take care of it. Like parts of the firmware, code, repo organization, images, and the internal side of the apps: CAD and EDA . Basically, that’s it, to sum up . I forgot to put the others Lapse"}, {"post_id": 57543, "ts": "2026-08-29T18:35:03Z", "hours": 1.2081, "text": "I’m done here! The two files we worked on are finished. Now we have the initializer and use of the MCP23017 (I’ll just write MCP from now on in this log) . The addresses have been mapped and the registers too. You can see what happens along with the logic of keeping the line in the LOW state and the rest HIGH . In this part, it’s necessary to use masks and bitwise operations to see how it works. It stays in a loop analyzing what was pressed and, of course, if something strange happens outside the configuration, it throws an error saying UNKNOWN ."}, {"post_id": 56813, "ts": "2026-08-28T18:53:29Z", "hours": 1.4183, "text": "I made a lot more progress on the firmware !! As I said, the functions , declarations , and general use of the ESP-IDF are standardized , so it’s simple to build by consulting materials: docs, example codes, usage with some peripherals and components, AI , etc. In this case, the use of I2C and SPI communication is also well organized. The drivers for the components I use don’t give you headaches for this. Previously, we had already been working on the ‘macros’ part, or rather the project HAL , even without knowing what it was. In the second image, there’s the keymap, made as a 7x7 matrix for the calculator - what the keys do. That’s already connected to the names of each key . The scanning was done, a loop that identifies which keys were used, and the rendering of the items on the display . Taking the data buffers and transitioning the communication with the ESP about what was pressed and how it will relay that to the screen. I think it’s interesting to mention: Explaining how key reading works with the MCP: each key is assigned by the matrix indices - row x column. The columns are set up with internal pull-up resistors, so when inactive they measure 3.3V (level 1). The ESP pulls the row to 0V (level 0), and when a key is pressed, it knows it because it reads !=0 from the column and matches it with the row it’s accessing to get the unique identifier for that key. That way you know 100% for sure what was pressed. And this cycle keeps running every few milliseconds."}, {"post_id": 56250, "ts": "2026-08-27T22:35:57Z", "hours": 0.6989, "text": "I got started at the base and analyzed the HAL (Hardware Abstraction Layer) of the project. I was studying some things, basically the functions and how to use the framework . I noticed that the functions are pretty standardized, like how to use registers, handle addressing, and use macros , directives/variables . Basically, the headers I was going to use and docs and things like that I was checking out, now speaking exclusively about the Aliexpress display that was in Mandarin (some of the ones I saw while researching) and offline I was tinkering and looking at some things, asking AI to explain and check things to move forward . I got the variant I was going to use, and later on it got analyzed and the board_pins.h ended up fine. I also started messing with the keypad, just defining it and later on how to monitor and use the identifiers of each key ."}, {"post_id": 55265, "ts": "2026-08-26T23:21:10Z", "hours": 0.9006, "text": "I started looking more closely at the firmware part ! Actually, I’ve never worked with ESP-IDF, so I’m going to take another good look at it and refresh myself on things I might not be prepared enough for. I grabbed it to check out and study with the example code \"Blynk Led\" —the one in the picture is a different one. It’s to control the internal LED with the BOOT button. I’ve seen a bit, and RTOS seems really cool, here it’s FreeRTOS . But you need to pay attention and be aware, understand how things work. I feel like it’s going to be a long and tough road… but let’s go! The good thing is that we have AI to help us out and clarify points, test stuff , and so on."}, {"post_id": 54514, "ts": "2026-08-25T15:21:59Z", "hours": 0.6925, "text": "I finished working on a few more things in the Assembly . I was aligning the cut positions in the view (remove extrude) and it took a while because the Mates , Fastened Mates created kind of restrictions that didn’t allow certain parts to move. Also put the 3D for the display. Then at the end I made the first commit to the repo! Lapse"}, {"post_id": 54126, "ts": "2026-08-24T23:04:44Z", "hours": 1.725, "text": "I just tweaked the parts a little more and then went to the Assembly . The PCB step was 50MB and took a while to load, and then when I tried to insert it, it didn’t load everything right after choosing a square option with a symbol similar to the Part Studio one, but eventually it worked. I used some fastened mates to join the items, and since this isn’t constant and there are hollow parts where you want to center/place in a specific spot, the Mate Connector doesn’t apply, so I used something like the transform to select the piece. That’s how I kept going until I got here! In the middle of the work, I had to edit the Part Studio because some points differed from the positioning and mounted parts of the PCB , like the USB and microSD . That’s it—work, found mistakes, fix them, and move forward! Lapse"}, {"post_id": 53863, "ts": "2026-08-24T15:49:47Z", "hours": 0.6503, "text": "What happened with the keypad being wrong was that in the sketch I dimensioned it incorrectly (swapped height for width) , and that’s why some of the blocks went beyond the edges and weren’t symmetrical. I imagined that might be it and fixed it . I made a rectangle there thinking about maybe adding a simple lens protection for the camera. After that, a rough idea of the cover that is usually used to protect the front part. Besides that, just a simple fillet on the sides. I did that, but I admit I might change this idea and its overall shape . Once I have everything in hand, I’ll update it to have a proper enclosure . Lapse"}, {"post_id": 53704, "ts": "2026-08-24T11:43:25Z", "hours": 1.1836, "text": "I finished the rear shell for the case. I made some bosses for the PCB fitting. It’s noticeable that the top right one is misaligned. I mentioned before that it’s because the traces and components were occupying that space, and when I remodeled it to 84x85 , the hole slots didn’t go along—they got lost on the canvas . Later I remembered, organized, and figured out a way to put them like this. Only one ended up 'strange,' which is NOT a problem at all. I made the shell 1.8mm thick and also cut the slot for the camera. I left the keypad at 74x80 , making a 7x7 feature pattern . This still bugs me because it doesn’t look right and the logic seems to change… I just need more experience and general practice to be ready for different scenarios. Some parts went out of place, but it’s just a matter of testing measurements until it works and maybe checking some guide videos on how to use this feature correctly . Lapse"}, {"post_id": 53406, "ts": "2026-08-23T22:58:39Z", "hours": 1.8672, "text": "I had made a Variable Studio but I end up not using it and don’t remember much. I asked the AI for help since I’ve never really worked with this item and it seemed better for standardizing and putting something defined that is used constantly. But in the end, I remember the quota values and some calculations are simple. Here I did the rear and front parts of the case, I didn’t do the extrusion there but it’s more or less correct. I had been thinking, and as I said, I worked on an idea and previous version, so it was actually pretty easy for that."}, {"post_id": 53124, "ts": "2026-08-23T15:34:18Z", "hours": 1.4269, "text": "I finished placing the holes on the PCB. Actually, I had forgotten… I was focused on finishing and trying to deliver something more professional in the routing part that when I finished I was like \"finally did it? Can I export the production files now?\" and the happiness and rush of the moment made it happen . It wasn’t possible to perfectly align the holes and the thought I had because of the traces I needed to place on the PCB, so it stayed like this. Only the top-right one ended up ‘different’. Now it’s just finishing the PCB and fixing the firmware . I was already checking and testing a bit offline."}, {"post_id": 51854, "ts": "2026-08-21T18:37:09Z", "hours": 3.1492, "text": "I routed a lot more! I tried, tried to optimize so I wouldn’t have to run traces on Inner1 , but it really wasn’t going to work. Partly because of the layout and distances of some ICs to the decoupling capacitors , practices for better signal quality . I forgot ( ) and it was already almost done , so I came here to post up to this point Lapse: Lapse"}, {"post_id": 50471, "ts": "2026-08-19T17:13:34Z", "hours": 3.94, "text": "Well, what happened. I went to check the price of the PCB – in this case, when exporting the GERBER it showed a price and it was pretty expensive, $33! The other 3 boards I made were within the 100x100 size and, if I’m not mistaken, the most expensive one was listed at $7. Here I’m kind of making different versions and testing, experimenting with what happens with certain configurations (size, traces, layers, type of components, price,…). I was putting it off and taking my time because I wanted to use what I had from the other one, but then I decided to start routing from scratch."}, {"post_id": 48112, "ts": "2026-08-16T12:20:20Z", "hours": 1.2892, "text": "I’ve practically finished the new schematic for the raw camera version. I managed to tidy up and properly organize the layout for this new part. First, I looked over it to see what I could add and prepare in positioning the new components for routing. The camera I left is one that uses an FPC connector . I’ve already put this item in place, arranged it with LDOs , translators , and controllers . Basically, it’s about handling the signals, how they occur, to make them compatible with the module I took and the rest of what I had already prepared. It got a bit messy because I really need to see how to place each item, and I wanted to make use of a large part of the general layout from the other PCB version … lapse"}, {"post_id": 47488, "ts": "2026-08-15T12:52:48Z", "hours": 1.2344, "text": "I made some changes and was researching a raw version with the OV5640 . To make it a more controlled and integrated work, and thinking about reducing it and making the aesthetics of the project look more like what it really is, reducing the thickness, I changed and added a lot of other components and I’m starting to organize them to be on the Bottom Layer. I need more LDOs , capacitors , and resistors . Simple, right? The passives and ‘controllers’ for electricity, current, voltage, etc. I’m not really knowing much about the impedance part, so I use ChatGPT to guide me, teach things, and think about the structure of the project, the PCB… Lapse: Lapse"}, {"post_id": 46376, "ts": "2026-08-13T15:31:34Z", "hours": 0.7503, "text": "Well, things were already going pretty well. Basically, I messed around a bit with the routes since the camera pins would be placed behind the PCB, like on the bottom. Then I changed the header layer and rerouted it. Now I managed to remove the header from the 3D preview (since the header was used to make the holes and get an idea of the position of the Arducam pin rows). When I have it in hand, I’ll solder everything directly onto the board. I was messing around a bit with other things too, in the firmware, doing research, checking data, etc. I used ChatGPT for that and even Antigravity. Then I moved forward with some things, checked, asked about the case. The thing is, I’m busy (or I should be) and couldn’t really do sessions and things of the project that I was working on to save. And then I really ended up forgetting to make the Lapses… a lot of times it was gradual work, bit by bit, and sometimes I’d go a while without touching it because I depended on my parents to call me or something like that, a pause. As far as I remember, I used to be able to edit the Lapses before, but I think it’s better to do it directly. All of this wasn’t just 17 minutes! I realized that there was a WakaTime extension for EasyEDA and Onshape. At the time (~ about 5 months ago) I didn’t know about Lapse or anything like that and ended up using this. I ended up creating more than one project to test things out, run tests, and see other people’s implementations. And it turned out they came out with very similar names and all. I didn’t remember the name anymore and I think I synced a few incorrectly. I fragmented the time. BUT REALLY MOST OF IT WAS BECAUSE I DIDN’T RECORD, ETC. I think you can add like 3 more hours"}, {"post_id": 43610, "ts": "2026-08-08T23:42:13Z", "hours": 1.5008, "text": "Well, I tweaked the PCB design just a little more. Actually, very little—I was just seeing if there was a way to handle the USB traces since these two NETs were 170mm and had a lot of vias . The center already had the other components and trace routing, so I guess there wasn’t much to do. And honestly, I’m not experienced, so I don’t know how to make these things better . Along with that, there’s roughly an idea of how the project case will look and the items I had already been working on."}, {"post_id": 41474, "ts": "2026-08-05T18:14:06Z", "hours": 0.9006, "text": "Finally the errors disappeared… it turns out you had the custom DRC rules that I set. Then, like 2 or 3 NETs had thickness rules that couldn’t be followed because QFN components and the VSON package type have pads really close to each other (pitch) , so there was no way to route 0.8mm traces on components with, like, 0.4mm pitch . Obviously, you had to reduce it to make it work, but I didn’t know by how much and whether it might be wrong at some point, cause problems, or lower the PCB’s lifespan. 😶 I figured out how to change the rules and get things fixed and done. Man, I think I should review it again and really check some automatic NETs from the editor. After all these days without touching this, I noticed there were these NETs without descriptive names . I don’t remember if it’s because I didn’t assign a NET, or if it’s just that connection between those pins or something like that. But overall it’s going to be easy. I really hope SO MUCH! Lapse Lapse"}, {"post_id": 41406, "ts": "2026-08-05T16:27:53Z", "hours": 4.0842, "text": "I’m back… I won’t be able to be very active here due to classes and coursework. I spent a good few hours working on this, but when I checked, it only showed 23 minutes… Maybe I linked the hours to the project incorrectly. Actually, there’s a file with the same name plus “_copy” at the end, and I thought I was already working on the right one. Well, I actually finished the routing. It turned out there were some copper islands that weren’t connecting to the rest of the pour, so I had to route them too. But to me, some of the ones flagging routing errors (showing ratsnests) didn’t look isolated and should have been able to join the copper plane. Oh well. The center ended up looking messy; that’s where the components—and consequently the traces—are concentrated. I’ll probably have to find a way to optimize and work on that. Plus, there are 39 DRC errors now… I hope I can submit this project; I’ve already done two others, but the deadline unfortunately ran out while I was optimizing things, addressing review comments, and dealing with components and budget issues. Oh, the way development work and hardware projects are recorded has also changed; now there are timelapses available here on Lapse : Lapse Lapse Lapse Lapse"}, {"post_id": 34370, "ts": "2026-07-25T00:59:26Z", "hours": 0.8669, "text": "I kept routing. I made the port expander matrix (the one on the FPC in the center left), the header for the camera, and practically all the ESP pins I’m still thinking about tidying it up a bit to reduce the number of traces going into the antenna area. There have to be traces coming there, it’s already acceptable as it is, but I will optimize… That’s kind of it."}, {"post_id": 34268, "ts": "2026-07-24T20:33:45Z", "hours": 2.6953, "text": "I was researching, looking at some more DOCS and just tidying up the last bits to start routing. I used Perplexity for some research and to cross-check data and see the trace widths for the NETs. I put DRC rules, so it’s much easier to work, because when you activate routing on a NET it automatically sets that thickness and rules in the project. I routed these more critical parts, power, data, a bit of the display part and stuff like that. Even with plenty of space, it already got a bit messy. This is my third board, so I’m still not that experienced with it. But this is the way to go. Most likely I won’t have to go back and change components. I just need to finish routing , think about the case and its mechanics What annoys me the most is having to return/exchange a component or it not being what I expect. In the case of marketplace sales, stores like Aliexpress"}, {"post_id": 33125, "ts": "2026-07-22T19:01:55Z", "hours": 0.7283, "text": "What I changed At the top, there’s the 2x11 header for the ArduCAM module—you just need to plug it in. I also added a few more devices (actually kind of switched around their positions and values). I hadn’t shown it before, but I imported this 3D model and linked it to the display device . I did a general cleanup and a lot more research , tests , t hings like that . I’m doing kinda okay. I kept waiting for the sellers to respond to me. But I didn’t get much, I could only get one reply per day. I would send messages there, but it was like 11hrs over there, outside their working hours. A lot of time for nothing… Also, that display manual/datasheet didn’t come with the dimensions of the display assembly, like the total height and the screen size I needed. I found it on a website, and it said 6mm, so I left that to do the 3D design to import the STEP as a 3D model. Another seller said they didn’t have the manufacturer’s data I needed for the camera to check the dimensions and the bus. I wanted one that was 3.3V , and usually it’s the common 22 or 24 pins. But random ones from Aliexpress can easily change something in the pinout or order, which breaks everything. Here I’m kind of developing the project blindly . It has to be a really precise version, and that’s difficult… I think I’m going to go with the ArduCam module. It’s not small or as modular as others, but for my case it’s probably okay. (until now YES)"}, {"post_id": 31507, "ts": "2026-07-19T23:30:21Z", "hours": 1.6856, "text": "As I said, I was going to send a message to the sellers, but I procrastinated, and by the time I sent it, it was already the weekend there. The sellers are Chinese, so their time zone is 11 hours ahead. Actually, it’s already Monday there now, so I think there’s no need to resend the message since mine is already in the queue (I hope…). Anyway, I messed around a bit more, organized the schematics a little better, added a few things, and thought about, more or less, how the items could/should be distributed on the PCB, so I did that with the images. So, this whole size isn’t totally necessary. It will help when routing, but there really aren’t any problems with that. What I might do is remove the part where the display goes since it will be securely framed in the future case. They sent the link to the display manual"}, {"post_id": 30148, "ts": "2026-07-17T14:17:14Z", "hours": 0.7, "text": "organizing schematics Here are the schematic pages I’m organizing: 01_SYSTEM_MCU , 02_POWER_USB , 03_KEYPAD_IO , 04_DISPLAY_STORAGE , Actually, I’m still missing one more schematic image: 05_CAMERA_TBD . It seems only four images are allowed per devlog. That’s it—trying to follow a logical organization, with a left-to-right flow and the power sections included :|"}, {"post_id": 29867, "ts": "2026-07-17T00:59:00Z", "hours": 1.255, "text": "I added a few more components. The thing is, I’m preparing how I’m going to connect the keyboard/MCP of the keys to the circuit, and for that, I’m going to use an FPC for it and other LDO parts. Parts that deal with inductance/decoupling and protection of the circuit components. I had to research and really look into things, and I’m already checking to find a module/version of the OV5640 with DVP FPC . I had to keep changing and reviewing the practical use of the components and kind of the electrical **‘needs’ **of the setup."}, {"post_id": 29153, "ts": "2026-07-15T21:01:04Z", "hours": 1.1164, "text": "I switched the MCP MCP23017 to a QFN type. I realized that in the end, everything was most likely going to be pretty big. The final product thickness is around 15mm or more. So now I’m studying and researching to change the components, organization, and then properly design the mechanics in CAD/case so everything stays stable. I didn’t really know the display dimensions. Some are kind of generic, with chip data/technical specifications giving a certain thickness, but most don’t have thickness. Looks like I’ll have to message the Aliexpress seller to get the exact data… I feel way more lost than I should. It’s annoying because I had already thought a bit at the start and there wasn’t supposed to be so many reconstructions/pivots in the project."}, {"post_id": 28238, "ts": "2026-07-14T11:46:50Z", "hours": 1.6344, "text": "Well, what I kept working on was the case. I was thinking that the right way is to make three separate parts: the back part where a phone case fits (thinking in this case), the front part where there are holes for the display, keys/buttons, etc., and the sliding cover with the tracks. This one, when using a normal calculator, usually fits on the back of the body and when not, it fits on the front, storing and protecting the screen. In my ideas, I asked Gemini to generate these images to help me clarify my thoughts and development. It turned out good! Another thing is that I noticed the display PCB module isn’t centered relative to the screen at all. Because of this, due to the width of the PCB and the case ending up close to the display module, it can’t be centered since there’s little free area for horizontal movement and the board would already touch the case walls. I made this 3D model to see roughly how it would look, and it looked weird. Not too much, but… The thing is, I usually do some stylizations, drawings, stuff like that. It would be possible to put a solar panel there, yeah, but I’m not going to go back much to that part of the EDA and rethink the system, mechanics, and circuit logic."}, {"post_id": 27633, "ts": "2026-07-13T12:05:34Z", "hours": 2.5256, "text": "I was supposed to post yesterday but my uncles came over and I didn’t get back to it at night here I’ve pretty much done the part that holds the PCB . The shell , I recessed inside it, and in the other picture you can see I made an Assembly to see how it was coming along and to have an idea of where the screw holes for the PCB are, and later what I should do on the case. I haven’t done this yet, but you can see some Mate Connectors in the picture of the case alone (the light blue, slightly grayish part) . I tried to make the holes, but the sketch planes and flat planes were on the top face and I couldn't make the holes . I spent some time trying that. I don’t know, but probably if I make a sketch on the bottom of the case I can make the holes. That’s it, 3D for EasyEDA , I’ve already fixed it in Onshape and I’m doing well with the case part. 🫡🙂"}, {"post_id": 27287, "ts": "2026-07-12T18:46:51Z", "hours": 1.1164, "text": "I finished tweaking a few more things in the PCB schematic and getting it ready to export a STEP to use as a base in Onshape. Actually, I made the display way too big, standardized at 10 or 15mm, but it should be something like ~2.8mm . The thing is, when I was moving some items around, it ended up moving the Board Outline too, even though I didn’t select it… so I locked it to prevent that from happening, and I’ve already done the same in Onshape . Now I’ll start on the case and then come back to routing"}, {"post_id": 26282, "ts": "2026-07-11T00:03:35Z", "hours": 1.0503, "text": "As I said, I didn’t see the dimensions of the full PCB for the 2.8 inch version , and because of that, I was going to need to change the board (since I don’t want to increase the size of the final product). So I went after the dimensions of the 2.4 inch version and made the rectangle just to represent the space it would take up in the PCB schematic. A strange thing is that when I went to change the 3D model of the device , instead of changing it, it added another part to it. I had to overlap them so it wouldn’t look so weird there in EasyEDA. Here is the image of parameters"}, {"post_id": 26039, "ts": "2026-07-10T16:52:05Z", "hours": 1.2689, "text": "I was getting ready to start routing, but then I decided to take a quick look at the schematic again and check if the power supply and protection/best practices part of the circuit was all good. I consulted Perplexity and it suggested adding resistors and changing a capacitor on the EN pin of the ESP. I changed it from 100nF to 1uF and added a 10kΩ resistor along with it. I had already added resistors to the SDA and SCL pins and I don’t remember if I changed that.. I also looked up the data for the external components. The display and the battery. I wanted to make a 3D model to make it look better and to get an idea in the EasyEDA rendering. I searched for the display data on the site, on its manufacturer’s website but found nothing. So I googled it and the data came up on a site already known here and there it was fine, that must be it, I needed the thickness in this case ~15mm. Ah, and I hadn’t noticed that the footprint I made for the display was only for the screen, not the complete module. Then I realized it’s going to be bigger than one of the PCB dimensions I had in mind… It’s supposed to be like that, I hadn’t noticed but in the image I attached with the green arrow it shows that it’s 50x86mm"}, {"post_id": 24935, "ts": "2026-07-08T20:19:46Z", "hours": 1.1667, "text": "more for PCB"}, {"post_id": 24848, "ts": "2026-07-08T17:59:50Z", "hours": 1.25, "text": "Here I made some mistakes… I thought I had done the footprints, but after entering the 3D view/rendering of the PCB, I saw that there are only holes in the devices I made (these two in the attached images). I made some area that is seen as non-outline or something like that of the PCB. So I’ll have to fix that 😑 I also made an area on the board that will not have PCB material (FR-4) under the chip/module ESP antenna. This and the 15 mm keepout area around the antenna are to avoid interfering with Wi-Fi and Bluetooth connectivity ."}, {"post_id": 24636, "ts": "2026-07-08T11:08:13Z", "hours": 1.0189, "text": "I kept working on the PCB schematic . After tidying it up a bit, I decided to make a device and footprint for the battery I’m going to use. It’s kind of standardized with dimensions of 10x34x50 , A type with 2000mAh. That’s it, I made a rectangle of 84 by 165mm and put some holes 5mm away from the edges. I still need to figure out what type I’ll use, whether it’s countersunk or not. But either way, between 2.2 and 3mm ."}, {"post_id": 24419, "ts": "2026-07-07T23:26:18Z", "hours": 1.8364, "text": "I’m still working on the schematic… I was finishing organizing things and then messing around with the PCB design at the end . I’m going to call it PCB SCHEMATIC . Earlier I changed the display to a 2.8 inch one because I realized it was going to be too big, and the style I’m going for is kind of like this Casio ClassWiz Here in the attached images are the drawings of the device and footprint ."}, {"post_id": 23722, "ts": "2026-07-06T20:42:28Z", "hours": 1.9294, "text": "Here I tried to fix the NETs of the components and connections. I looked for the datasheets of the devices I’m using (it was easy since I just had to go back to LCSC with the Part Numbers , and on its page, the datasheet is already there ). I downloaded them, some in English, others in Asian languages (I think if I remember correctly there was only Mandarin and Korean). I uploaded them to NotebookLM, and it gave me an overview of how things worked and pin data, that kind of stuff . I saw that I had done some things wrong yesterday, so I had to fix the labels and that kind of stuff."}, {"post_id": 22336, "ts": "2026-07-04T19:13:23Z", "hours": 2.0931, "text": "I created another device—just to simulate the 3.5 LCD display I found on AliExpress. After doing some research and looking at other options, I decided against using Seeed’s S3 Sense. It comes with an OV2640 camera, but I’m going to use an external OV5640 module instead—a 5MP one I bought along with the other two . I did some research, checked out components and versions in the LCSC library , verified a few things with Perplexity, and added the items to the schematic. It’s still pretty messy, but I’ll clean it up, organize it, and get the NET’s sorted out later."}, {"post_id": 21583, "ts": "2026-07-03T16:47:05Z", "hours": 0.7672, "text": "Well, I started this project here… the idea I had was to make a node that is a ‘calculator’ from scratch. I’m not exactly sure if I’ll include multiple buttons or common functions in it, because the difference with this one is having access to the AI API, and I’m also thinking about adding Wolfram Alpha. It’s going to have a camera to take a picture of the equation, send it to the API, and it returns an image of the solution. It connects to Wi-Fi and sends the data to a server where it’s processed, formatted in LaTeX, and then returns the image. So I started by putting the components in the EasyEDA schematic and created a simple device that was supposed to be the Seeed Xiao ESP32 S3"}]...
|
Title: ∇Calc by @EngThi | Stardance
Devlogs:
Well Title: ∇Calc by @EngThi | Stardance
Devlogs:
Well, I started this project here… the idea I had was to make a node that is a ‘calculator’ from scratch. I’m not exactly sure if I’ll include multiple buttons or common functions in it, because the difference with this one is having access to the AI API, and I’m also thinking about adding Wolfram Alpha. It’s going to have a camera to take a picture of the equation, send it to the API, and it returns an image of the solution. It connects to Wi-Fi and sends the data to a server where it’s processed, formatted in LaTeX, and then returns the image. So I started by putting the components in the EasyEDA schematic and created a simple device that was supposed to be the Seeed Xiao ESP32 S3
I created another device—just to simulate the 3.5 LCD display I found on AliExpress. After doing some research and looking at other options, I decided against using Seeed’s S3 Sense. It comes with an OV2640 camera, but I’m going to use an external OV5640 module instead—a 5MP one I bought along with the other two . I did some research, checked out components and versions in the LCSC library , verified a few things with Perplexity, and added the items to the schematic. It’s still pretty messy, but I’ll clean it up, organize it, and get the NET’s sorted out later.
Here I tried to fix the NETs of the components and connections. I looked for the datasheets of the devices I’m using (it was easy since I just had to go back to LCSC with the Part Numbers , and on its page, the datasheet is already there ). I downloaded them, some in English, others in Asian languages (I think if I remember correctly there was only Mandarin and Korean). I uploaded them to NotebookLM, and it gave me an overview of how things worked and pin data, that kind of stuff . I saw that I had done some things wrong yesterday, so I had to fix the labels and that kind of stuff.
I’m still working on the schematic… I was finishing organizing things and then messing around with the PCB design at the end . I’m going to call it PCB SCHEMATIC . Earlier I changed the display to a 2.8 inch one because I realized it was going to be too big, and the style I’m going for is kind of like this Casio ClassWiz Here in the attached images are the drawings of the device and footprint .
I kept working on the PCB schematic . After tidying it up a bit, I decided to make a device and footprint for the battery I’m going to use. It’s kind of standardized with dimensions of 10x34x50 , A type with 2000mAh. That’s it, I made a rectangle of 84 by 165mm and put some holes 5mm away from the edges. I still need to figure out what type I’ll use, whether it’s countersunk or not. But either way, between 2.2 and 3mm .
Here I made some mistakes… I thought I had done the footprints, but after entering the 3D view/rendering of the PCB, I saw that there are only holes in the devices I made (these two in the attached images). I made some area that is seen as non-outline or something like that of the PCB. So I’ll have to fix that 😑 I also made an area on the board that will not have PCB material (FR-4) under the chip/module ESP antenna. This and the 15 mm keepout area around the antenna are to avoid interfering with Wi-Fi and Bluetooth connectivity .
more for PCB
I was getting ready to start routing, but then I decided to take a quick look at the schematic again and check if the power supply and protection/best practices part of the circuit was all good. I consulted Perplexity and it suggested adding resistors and changing a capacitor on the EN pin of the ESP. I changed it from 100nF to 1uF and added a 10kΩ resistor along with it. I had already added resistors to the SDA and SCL pins and I don’t remember if I changed that.. I also looked up the data for the external components. The display and the battery. I wanted to make a 3D model to make it look better and to get an idea in the EasyEDA rendering. I searched for the display data on the site, on its manufacturer’s website but found nothing. So I googled it and the data came up on a site already known here and there it was fine, that must be it, I needed the thickness in this case ~15mm. Ah, and I hadn’t noticed that the footprint I made for the display was only for the screen, not the complete module. Then I realized it’s going to be bigger than one of the PCB dimensions I had in mind… It’s supposed to be like that, I hadn’t noticed but in the image I attached with the green arrow it shows that it’s 50x86mm
As I said, I didn’t see the dimensions of the full PCB for the 2.8 inch version , and because of that, I was going to need to change the board (since I don’t want to increase the size of the final product). So I went after the dimensions of the 2.4 inch version and made the rectangle just to represent the space it would take up in the PCB schematic. A strange thing is that when I went to change the 3D model of the device , instead of changing it, it added another part to it. I had to overlap them so it wouldn’t look so weird there in EasyEDA. Here is the image of parameters
I finished tweaking a few more things in the PCB schematic and getting it ready to export a STEP to use as a base in Onshape. Actually, I made the display way too big, standardized at 10 or 15mm, but it should be something like ~2.8mm . The thing is, when I was moving some items around, it ended up moving the Board Outline too, even though I didn’t select it… so I locked it to prevent that from happening, and I’ve already done the same in Onshape . Now I’ll start on the case and then come back to routing
I was supposed to post yesterday but my uncles came over and I didn’t get back to it at night here I’ve pretty much done the part that holds the PCB . The shell , I recessed inside it, and in the other picture you can see I made an Assembly to see how it was coming along and to have an idea of where the screw holes for the PCB are, and later what I should do on the case. I haven’t done this yet, but you can see some Mate Connectors in the picture of the case alone (the light blue, slightly grayish part) . I tried to make the holes, but the sketch planes and flat planes were on the top face and I couldn't make the holes . I spent some time trying that. I don’t know, but probably if I make a sketch on the bottom of the case I can make the holes. That’s it, 3D for EasyEDA , I’ve already fixed it in Onshape and I’m doing well with the case part. 🫡🙂
Well, what I kept working on was the case. I was thinking that the right way is to make three separate parts: the back part where a phone case fits (thinking in this case), the front part where there are holes for the display, keys/buttons, etc., and the sliding cover with the tracks. This one, when using a normal calculator, usually fits on the back of the body and when not, it fits on the front, storing and protecting the screen. In my ideas, I asked Gemini to generate these images to help me clarify my thoughts and development. It turned out good! Another thing is that I noticed the display PCB module isn’t centered relative to the screen at all. Because of this, due to the width of the PCB and the case ending up close to the display module, it can’t be centered since there’s little free area for horizontal movement and the board would already touch the case walls. I made this 3D model to see roughly how it would look, and it looked weird. Not too much, but… The thing is, I usually do some stylizations, drawings, stuff like that. It would be possible to put a solar panel there, yeah, but I’m not going to go back much to that part of the EDA and rethink the system, mechanics, and circuit logic.
I switched the MCP MCP23017 to a QFN type. I realized that in the end, everything was most likely going to be pretty big. The final product thickness is around 15mm or more. So now I’m studying and researching to change the components, organization, and then properly design the mechanics in CAD/case so everything stays stable. I didn’t really know the display dimensions. Some are kind of generic, with chip data/technical specifications giving a certain thickness, but most don’t have thickness. Looks like I’ll have to message the Aliexpress seller to get the exact data… I feel way more lost than I should. It’s annoying because I had already thought a bit at the start and there wasn’t supposed to be so many reconstructions/pivots in the project.
I added a few more components. The thing is, I’m preparing how I’m going to connect the keyboard/MCP of the keys to the circuit, and for that, I’m going to use an FPC for it and other LDO parts. Parts that deal with inductance/decoupling and protection of the circuit components. I had to research and really look into things, and I’m already checking to find a module/version of the OV5640 with DVP FPC . I had to keep changing and reviewing the practical use of the components and kind of the electrical **‘needs’ **of the setup.
organizing schematics Here are the schematic pages I’m organizing: 01_SYSTEM_MCU , 02_POWER_USB , 03_KEYPAD_IO , 04_DISPLAY_STORAGE , Actually, I’m still missing one more schematic image: 05_CAMERA_TBD . It seems only four images are allowed per devlog. That’s it—trying to follow a logical organization, with a left-to-right flow and the power sections included :|
As I said, I was going to send a message to the sellers, but I procrastinated, and by the time I sent it, it was already the weekend there. The sellers are Chinese, so their time zone is 11 hours ahead. Actually, it’s already Monday there now, so I think there’s no need to resend the message since mine is already in the queue (I hope…). Anyway, I messed around a bit more, organized the schematics a little better, added a few things, and thought about, more or less, how the items could/should be distributed on the PCB, so I did that with the images. So, this whole size isn’t totally necessary. It will help when routing, but there really aren’t any problems with that. What I might do is remove the part where the display goes since it will be securely framed in the future case. They sent the link to the display manual
What I changed At the top, there’s the 2x11 header for the ArduCAM module—you just need to plug it in. I also added a few more devices (actually kind of switched around their positions and values). I hadn’t shown it before, but I imported this 3D model and linked it to the display device . I did a general cleanup and a lot more research , tests , t hings like that . I’m doing kinda okay. I kept waiting for the sellers to respond to me. But I didn’t get much, I could only get one reply per day. I would send messages there, but it was like 11hrs over there, outside their working hours. A lot of time for nothing… Also, that display manual/datasheet didn’t come with the dimensions of the display assembly, like the total height and the screen size I needed. I found it on a website, and it said 6mm, so I left that to do the 3D design to import the STEP as a 3D model. Another seller said they didn’t have the manufacturer’s data I needed for the camera to check the dimensions and the bus. I wanted one that was 3.3V , and usually it’s the common 22 or 24 pins. But random ones from Aliexpress can easily change something in the pinout or order, which breaks everything. Here I’m kind of developing the project blindly . It has to be a really precise version, and that’s difficult… I think I’m going to go with the ArduCam module. It’s not small or as modular as others, but for my case it’s probably okay. (until now YES)
I was researching, looking at some more DOCS and just tidying up the last bits to start routing. I used Perplexity for some research and to cross-check data and see the trace widths for the NETs. I put DRC rules, so it’s much easier to work, because when you activate routing on a NET it automatically sets that thickness and rules in the project. I routed these more critical parts, power, data, a bit of the display part and stuff like that. Even with plenty of space, it already got a bit messy. This is my third board, so I’m still not that experienced with it. But this is the way to go. Most likely I won’t have to go back and change components. I just need to finish routing , think about the case and its mechanics What annoys me the most is having to return/exchange a component or it not being what I expect. In the case of marketplace sales, stores like Aliexpress
I kept routing. I made the port expander matrix (the one on the FPC in the center left), the header for the camera, and practically all the ESP pins I’m still thinking about tidying it up a bit to reduce the number of traces going into the antenna area. There have to be traces coming there, it’s already acceptable as it is, but I will optimize… That’s kind of it.
I’m back… I won’t be able to be very active here due to classes and coursework. I spent a good few hours working on this, but when I checked, it only showed 23 minutes… Maybe I linked the hours to the project incorrectly. Actually, there’s a file with the same name plus “_copy” at the end, and I thought I was already working on the right one. Well, I actually finished the routing. It turned out there were some copper islands that weren’t connecting to the rest of the pour, so I had to route them too. But to me, some of the ones flagging routing errors (showing ratsnests) didn’t look isolated and should have been able to join the copper plane. Oh well. The center ended up looking messy; that’s where the components—and consequently the traces—are concentrated. I’ll probably have to find a way to optimize and work on that. Plus, there are 39 DRC errors now… I hope I can submit this project; I’ve already done two others, but the deadline unfortunately ran out while I was optimizing things, addressing review comments, and dealing with components and budget issues. Oh, the way development work and hardware projects are recorded has also changed; now there are timelapses available here on Lapse : Lapse Lapse Lapse Lapse
Finally the errors disappeared… it turns out you had the custom DRC rules that I set. Then, like 2 or 3 NETs had thickness rules that couldn’t be followed because QFN components and the VSON package type have pads really close to each other (pitch) , so there was no way to route 0.8mm traces on components with, like, 0.4mm pitch . Obviously, you had to reduce it to make it work, but I didn’t know by how much and whether it might be wrong at some point, cause problems, or lower the PCB’s lifespan. 😶 I figured out how to change the rules and get things fixed and done. Man, I think I should review it again and really check some automatic NETs from the editor. After all these days without touching this, I noticed there were these NETs without descriptive names . I don’t remember if it’s because I didn’t assign a NET, or if it’s just that connection between those pins or something like that. But overall it’s going to be easy. I really hope SO MUCH! Lapse Lapse
Well, I tweaked the PCB design just a little more. Actually, very little—I was just seeing if there was a way to handle the USB traces since these two NETs were 170mm and had a lot of vias . The center already had the other components and trace routing, so I guess there wasn’t much to do. And honestly, I’m not experienced, so I don’t know how to make these things better . Along with that, there’s roughly an idea of how the project case will look and the items I had already been working on.
Well, things were already going pretty well. Basically, I messed around a bit with the routes since the camera pins would be placed behind the PCB, like on the bottom. Then I changed the header layer and rerouted it. Now I managed to remove the header from the 3D preview (since the header was used to make the holes and get an idea of the position of the Arducam pin rows). When I have it in hand, I’ll solder everything directly onto the board. I was messing around a bit with other things too, in the firmware, doing research, checking data, etc. I used ChatGPT for that and even Antigravity. Then I moved forward with some things, checked, asked about the case. The thing is, I’m busy (or I should be) and couldn’t really do sessions and things of the project that I was working on to save. And then I really ended up forgetting to make the Lapses… a lot of times it was gradual work, bit by bit, and sometimes I’d go a while without touching it because I depended on my parents to call me or something like that, a pause. As far as I remember, I used to be able to edit the Lapses before, but I think it’s better to do it directly. All of this wasn’t just 17 minutes! I realized that there was a WakaTime extension for EasyEDA and Onshape. At the time (~ about 5 months ago) I didn’t know about Lapse or anything like that and ended up using this. I ended up creating more than one project to test things out, run tests, and see other people’s implementations. And it turned out they came out with very similar names and all. I didn’t remember the name anymore and I think I synced a few incorrectly. I fragmented the time. BUT REALLY MOST OF IT WAS BECAUSE I DIDN’T RECORD, ETC. I think you can add like 3 more hours
I made some changes and was researching a raw version with the OV5640 . To make it a more controlled and integrated work, and thinking about reducing it and making the aesthetics of the project look more like what it really is, reducing the thickness, I changed and added a lot of other components and I’m starting to organize them to be on the Bottom Layer. I need more LDOs , capacitors , and resistors . Simple, right? The passives and ‘controllers’ for electricity, current, voltage, etc. I’m not really knowing much about the impedance part, so I use ChatGPT to guide me, teach things, and think about the structure of the project, the PCB… Lapse: Lapse
I’ve practically finished the new schematic for the raw camera version. I managed to tidy up and properly organize the layout for this new part. First, I looked over it to see what I could add and prepare in positioning the new components for routing. The camera I left is one that uses an FPC connector . I’ve already put this item in place, arranged it with LDOs , translators , and controllers . Basically, it’s about handling the signals, how they occur, to make them compatible with the module I took and the rest of what I had already prepared. It got a bit messy because I really need to see how to place each item, and I wanted to make use of a large part of the general layout from the other PCB version … lapse
Well, what happened. I went to check the price of the PCB – in this case, when exporting the GERBER it showed a price and it was pretty expensive, $33! The other 3 boards I made were within the 100x100 size and, if I’m not mistaken, the most expensive one was listed at $7. Here I’m kind of making different versions and testing, experimenting with what happens with certain configurations (size, traces, layers, type of components, price,…). I was putting it off and taking my time because I wanted to use what I had from the other one, but then I decided to start routing from scratch.
I routed a lot more! I tried, tried to optimize so I wouldn’t have to run traces on Inner1 , but it really wasn’t going to work. Partly because of the layout and distances of some ICs to the decoupling capacitors , practices for better signal quality . I forgot ( ) and it was already almost done , so I came here to post up to this point Lapse: Lapse
I finished placing the holes on the PCB. Actually, I had forgotten… I was focused on finishing and trying to deliver something more professional in the routing part that when I finished I was like "finally did it? Can I export the production files now?" and the happiness and rush of the moment made it happen . It wasn’t possible to perfectly align the holes and the thought I had because of the traces I needed to place on the PCB, so it stayed like this. Only the top-right one ended up ‘different’. Now it’s just finishing the PCB and fixing the firmware . I was already checking and testing a bit offline.
I had made a Variable Studio but I end up not using it and don’t remember much. I asked the AI for help since I’ve never really worked with this item and it seemed better for standardizing and putting something defined that is used constantly. But in the end, I remember the quota values and some calculations are simple. Here I did the rear and front parts of the case, I didn’t do the extrusion there but it’s more or less correct. I had been thinking, and as I said, I worked on an idea and previous version, so it was actually pretty easy for that.
I finished the rear shell for the case. I made some bosses for the PCB fitting. It’s noticeable that the top right one is misaligned. I mentioned before that it’s because the traces and components were occupying that space, and when I remodeled it to 84x85 , the hole slots didn’t go along—they got lost on the canvas . Later I remembered, organized, and figured out a way to put them like this. Only one ended up 'strange,' which is NOT a problem at all. I made the shell 1.8mm thick and also cut the slot for the camera. I left the keypad at 74x80 , making a 7x7 feature pattern . This still bugs me because it doesn’t look right and the logic seems to change… I just need more experience and general practice to be ready for different scenarios. Some parts went out of place, but it’s just a matter of testing measurements until it works and maybe checking some guide videos on how to use this feature correctly . Lapse
What happened with the keypad being wrong was that in the sketch I dimensioned it incorrectly (swapped height for width) , and that’s why some of the blocks went beyond the edges and weren’t symmetrical. I imagined that might be it and fixed it . I made a rectangle there thinking about maybe adding a simple lens protection for the camera. After that, a rough idea of the cover that is usually used to protect the front part. Besides that, just a simple fillet on the sides. I did that, but I admit I might change this idea and its overall shape . Once I have everything in hand, I’ll update it to have a proper enclosure . Lapse
I just tweaked the parts a little more and then went to the Assembly . The PCB step was 50MB and took a while to load, and then when I tried to insert it, it didn’t load everything right after choosing a square option with a symbol similar to the Part Studio one, but eventually it worked. I used some fastened mates to join the items, and since this isn’t constant and there are hollow parts where you want to center/place in a specific spot, the Mate Connector doesn’t apply, so I used something like the transform to select the piece. That’s how I kept going until I got here! In the middle of the work, I had to edit the Part Studio because some points differed from the positioning and mounted parts of the PCB , like the USB and microSD . That’s it—work, found mistakes, fix them, and move forward! Lapse
I finished working on a few more things in the Assembly . I was aligning the cut positions in the view (remove extrude) and it took a while because the Mates , Fastened Mates created kind of restrictions that didn’t allow certain parts to move. Also put the 3D for the display. Then at the end I made the first commit to the repo! Lapse
I started looking more closely at the firmware part ! Actually, I’ve never worked with ESP-IDF, so I’m going to take another good look at it and refresh myself on things I might not be prepared enough for. I grabbed it to check out and study with the example code "Blynk Led" —the one in the picture is a different one. It’s to control the internal LED with the BOOT button. I’ve seen a bit, and RTOS seems really cool, here it’s FreeRTOS . But you need to pay attention and be aware, understand how things work. I feel like it’s going to be a long and tough road… but let’s go! The good thing is that we have AI to help us out and clarify points, test stuff , and so on.
I got started at the base and analyzed the HAL (Hardware Abstraction Layer) of the project. I was studying some things, basically the functions and how to use the framework . I noticed that the functions are pretty standardized, like how to use registers, handle addressing, and use macros , directives/variables . Basically, the headers I was going to use and docs and things like that I was checking out, now speaking exclusively about the Aliexpress display that was in Mandarin (some of the ones I saw while researching) and offline I was tinkering and looking at some things, asking AI to explain and check things to move forward . I got the variant I was going to use, and later on it got analyzed and the board_pins.h ended up fine. I also started messing with the keypad, just defining it and later on how to monitor and use the identifiers of each key .
I made a lot more progress on the firmware !! As I said, the functions , declarations , and general use of the ESP-IDF are standardized , so it’s simple to build by consulting materials: docs, example codes, usage with some peripherals and components, AI , etc. In this case, the use of I2C and SPI communication is also well organized. The drivers for the components I use don’t give you headaches for this. Previously, we had already been working on the ‘macros’ part, or rather the project HAL , even without knowing what it was. In the second image, there’s the keymap, made as a 7x7 matrix for the calculator - what the keys do. That’s already connected to the names of each key . The scanning was done, a loop that identifies which keys were used, and the rendering of the items on the display . Taking the data buffers and transitioning the communication with the ESP about what was pressed and how it will relay that to the screen. I think it’s interesting to mention: Explaining how key reading works with the MCP: each key is assigned by the matrix indices - row x column. The columns are set up with internal pull-up resistors, so when inactive they measure 3.3V (level 1). The ESP pulls the row to 0V (level 0), and when a key is pressed, it knows it because it reads !=0 from the column and matches it with the row it’s accessing to get the unique identifier for that key. That way you know 100% for sure what was pressed. And this cycle keeps running every few milliseconds.
I’m done here! The two files we worked on are finished. Now we have the initializer and use of the MCP23017 (I’ll just write MCP from now on in this log) . The addresses have been mapped and the registers too. You can see what happens along with the logic of keeping the line in the LOW state and the rest HIGH . In this part, it’s necessary to use masks and bitwise operations to see how it works. It stays in a loop analyzing what was pressed and, of course, if something strange happens outside the configuration, it throws an error saying UNKNOWN .
its possible only four images… I fiddled a bit more with these items, files 📁 , repo organization , stuff like that . Also, I took screenshots of some views from the project’s mechanical render … I’m not really focusing on any one part, but I tinker a bit here and if I remember something I should have done or think could be better, I take care of it. Like parts of the firmware, code, repo organization, images, and the internal side of the apps: CAD and EDA . Basically, that’s it, to sum up . I forgot to put the others Lapse
more docs things right these Well, I tidied up the README and organized the folders and file names better. The repo in general . The other image is because I think I didn’t show it properly here and I was reposting , checking items and analyzing anything left there on EasyEDA
almost ready to submit!!! Finished and I’m getting ready to submit the project for review! I took some new renders and also did the prices part for the project items. I have everything here now and it is looking nice. Like I said before, I left some points to see and change better on the case when I have everything in my hands, so I can prototype 🤖 it better. I don’t have much skill with soldering, so I really hope I can get the Top PCBA . This is all really cool and interesting that I was able to do, and I’m really happy about it. At the end I also organized things a little more and changed stuff to track what is needed in the repo , help anyone that wants to look at it or reproduce the project somehow. The System architecture section got really cool in the translation and organization, AI did that . I don’t really know how to make this type of diagram myself yet :/ I hope I didn’t forget anything and that the organization I made, and later asked to improve, documents the state well. Basically I: I finished organizing the repo, checking the prices, calculations , etc., taking screenshots , I kept iterating in the repo, editing, moving things , that kind of organization 🗂️
I’m back! Finalized the second PCB for the keys Well, yeah, I’m here again. I’m back, it’s been a while since I was away, right? I waited for things to settle down here so I could continue with the project. Yeah, and I finalized the idea of making a board on the second PCB there, where the buttons will be, you know, the clicks to use the calculator keys . And this here was kind of leftover code organization I was doing in the repository . I ended up not remembering everything from the project, but now I’m here again. So I’ll finish this up. It was pretty simple, I didn’t record it. But basically, I made a 7x7 matrix of switches , the buttons. Along with that, there’s the FPC connector to actually connect the board to the ribbon, to the rest of the MCP expander. I’m going to tidy it up a bit. The board also ended up being quite small 84x78 basically just to fit there, it would provide support and, you know, fit the switches at the distances that had already been predetermined in the case , right in the middle of the product’s housing. And then, along with that, the schematic is also simple, I just put an FPC connector , that’s all that’s really needed, and the buttons, the switches. Really simple. I think it’s interesting to mention (diodes & debounce): I was also going to use, you know, I was looking, people were saying, it’s good to use diodes , but just to kind of reduce debounce , fix certain issues, but it wouldn’t be that necessary, since the contacts closing would almost never happen like, I don’t know, three clicks at once, one next to the other. So that doesn’t really cause a problem where the ESP wouldn’t know exactly which key is being pressed and what it should do with the signal it’s receiving. And depending on how you study it and see how to handle it in the firmware , it actually wouldn’t even be that necessary to put these diodes on each of these buttons for that.
Keypad PCB done! Top & Bottom preview Now that I’ve finished, I’ve completed the PCB both images, the top and the bottom . I left the spaces for the M2 screws and already rotated everything, it was pretty easy! Basically, I kind of left an array, a 7x7 matrix . The keys would be more or less standardized and the only difference would be in the pad — like, in the rubber, the material that you press to trigger that key. That kind of thing. It turned out pretty nice. It’s simple, it’s actually simple to do this part, this kind of thing… That’s how it turned out. I’m not sure if I’ll tweak it much to add things like a D-pad or other types of keys for navigation, functions, the numeric keypad itself , that kind of stuff.
It’s kind of funny that I messed with this again, but basically this is a version where I repositioned the buttons and pins because, well, I decided the keys aren’t going to stay as a plain square matrix. So I kind of organized and divided things there to get a better idea of how the pins will be placed roughly around the center. On the top part, there’s sort of that D-pad area (not an actual single pad, but the individual buttons for that navigation). That circular button style you see on game controllers, handhelds , and on some other calculators too. I also moved the FPC connector over to the corner so it’s way easier and cleaner to connect everything up . On top of that, I rounded the board edges in this version. Overall, that was pretty much it! Lapse: Lapse
For now I’m working on the CAD ; I had finished the PCB. I put up a quick video of how it turned out I recorded it with Canva, which I’d used before for a school project, and it works. I even have the Spectacle app for Linux , but it records in 720p, which looks kind of bad, so recording it online through Canva ends up looking way better. Basically, it has the dimensions of part two , which I was rethinking and everything. And well, this was more or less the idea I had: there’s the front part for the buttons, and in this other version, it was supposed to have a passage for a circuit board to fit a small solar cell ☀️ . Depending on what I can find around the house and if there’s any leftover space in the casing (it’s pretty much ready), I might implement it even if it ends up mounted on the outside rather than inside the case, just for reuse and photovoltaic charging. Then I also put the back part together: the little hole for the camera 📷 , the slider for its protection, and on the side, the microSD card slot. The keymat for the buttons which I changed the layout of, so it’s not square anymore now has roughly the positions for all 49 keys and the holes where the support bosses will go. There’s also that little strip/rectangle, which is meant to be the protective cover fitting right into the other slot. Basically, that’s it! I’ll continue and tweak it later. It’s not too difficult, and I think it’ll be finished soon.
I just finished redoing the parts of the case the parts there and everything else in the project after this second round. This last one that was missing was from Part Studio 4 , which was the little slider drawer for camera privacy and protection on the back 🔒 , along with Part Studio 5 where I made the sliding lid/cover. Very, very simple. I also added some small slots there just to give it a nice tactile texture/grip — pretty small, with a 0.350 mm cut extrusion (removing material). That was kind of the piece I was still missing. It was simple and quick since I already had the basic idea from earlier attempts. Oh, and one thing I think I forgot to mention before: I imported .DXF files into the sketch to help guide the drawings, basically defining the extrusions for the parts. It turned out pretty good! To wrap up, I added what I had forgotten before: the mounting holes on the back cover bosses. Put 1.6mm holes there to hold the screws properly ⚙️ ....
|
1792806741.0958614
|
1793411541.0958614
|
|
8966
|
by @X | Stardance
|
X
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: by @X | Stardance
|
1792590576.19677
|
1793195376.19677
|
|
21337
|
“Make your Robot better!” Magical Wand by @M00nAng “Make your Robot better!” Magical Wand by @M00nAng3l | Stardance...
|
M00nAng3l
|
0
|
2.3
|
0
|
[]
|
[{"post_id": 33556, "ts": "202 [{"post_id": 33556, "ts": "2026-07-23T16:18:11Z", "hours": 0.75, "text": "onshape is lagging and is being quite difficult atm"}, {"post_id": 33491, "ts": "2026-07-23T14:11:07Z", "hours": 0.3167, "text": "Revised Design sketch after test print was completed. The things i changed were that im making the wand into keychain so it prints faster and its easier to wand out at events. I also revised the placing of the top parts shapes from the FIRST Robotics logo."}, {"post_id": 32498, "ts": "2026-07-21T18:34:46Z", "hours": 0.8669, "text": "Finished the CAD design for the wand. It’s ready to go to the printer now. I may make another version down the line but as a coming back to using CAD it was good to start with."}, {"post_id": 32452, "ts": "2026-07-21T17:30:31Z", "hours": 0.3667, "text": "Design sketch finished! The wand is Ready for Prototyping in onshape!"}]...
|
Title: “Make your Robot better!” Magical Wand by @ Title: “Make your Robot better!” Magical Wand by @M00nAng3l | Stardance
Devlogs:
Design sketch finished! The wand is Ready for Prototyping in onshape!
Finished the CAD design for the wand. It’s ready to go to the printer now. I may make another version down the line but as a coming back to using CAD it was good to start with.
Revised Design sketch after test print was completed. The things i changed were that im making the wand into keychain so it prints faster and its easier to wand out at events. I also revised the placing of the top parts shapes from the FIRST Robotics logo.
onshape is lagging and is being quite difficult atm...
|
1792781272.8282323
|
1793386072.8282323
|
|
2235
|
“Am I Cooked?” life simulator by @elizabeth | Star “Am I Cooked?” life simulator by @elizabeth | Stardance...
|
elizabeth
|
1
|
3.0
|
44
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-07T15:19:26Z", "hours": 3.0, "multiplier": 14.08, "payout": 44, "blessing": "neutral", "text": "I made “Am I Cooked?”, a life simulator where your choices decide your future. The idea actually came from my friends we were brainstorming project ideas for me to make for stardance when one of them looked at something happening and said, “Bro, they’re so cooked.” We all laughed, and that’s how the idea clicked. The hardest part was getting all the choices and endings to work properly. I’m proud of turning a random joke into a fun, playable game with multiple paths. Try making different choices each time you play, and let me know if you find any bugs or have ideas to make it even better!", "repo": "https://github.com/Elizadev41/-Am-I-Cooked-life-simulator", "demo": "https://elizadev41.github.io/-Am-I-Cooked-life-simulator/"}]...
|
[{"post_id": 14398, "ts": "202 [{"post_id": 14398, "ts": "2026-06-23T14:52:09Z", "hours": 0.4872, "text": "hellooo remembered this project Worked on Am I Cooked? today and added a bunch of new stuff. The game now has more categories and way more scenarios, so it should feel less repetitive. Each category has 10 scenarios now, and I added new ones like Work, Party, and Gaming. Chaos Mode actually works now too. Before it was mostly just a theme change, but now it randomly changes how much each choice affects your cooked score, so bad choices can get worse and sometimes weird stuff happens. I also added better endings based on your final score, so the results feel more personalized instead of just one basic ending. Current categories: School Sports Social Life Work Party Gaming Still planning to add more polish later, like stats, achievements, animations, and maybe better sharing."}, {"post_id": 7743, "ts": "2026-06-12T22:38:58Z", "hours": 0.4406, "text": "Fixed settings button Added settings menu Added music on/off Added game mode Added How to Play screen Added name welcome screen Added category picking Added score prediction Added results screen Added different colors for each game mode Made buttons and screens look better thats all for now guys byee this took me more time but i didnt post a devlog so i lost the timee"}, {"post_id": 7200, "ts": "2026-06-12T00:50:15Z", "hours": 0.4167, "text": "added a settings button"}, {"post_id": 3797, "ts": "2026-06-06T21:02:28Z", "hours": 0.6306, "text": "made a readme"}, {"post_id": 1247, "ts": "2026-06-03T03:11:23Z", "hours": 0.9383, "text": "made it pink and added mor scenarios+ turned it into a cyoa game"}, {"post_id": 500, "ts": "2026-06-01T23:40:50Z", "hours": 0.3653, "text": "base code done"}]...
|
Title: “Am I Cooked?” life simulator by @elizabeth Title: “Am I Cooked?” life simulator by @elizabeth | Stardance
Devlogs:
base code done
made it pink and added mor scenarios+ turned it into a cyoa game
made a readme
added a settings button
Fixed settings button Added settings menu Added music on/off Added game mode Added How to Play screen Added name welcome screen Added category picking Added score prediction Added results screen Added different colors for each game mode Made buttons and screens look better thats all for now guys byee this took me more time but i didnt post a devlog so i lost the timee
hellooo remembered this project Worked on Am I Cooked? today and added a bunch of new stuff. The game now has more categories and way more scenarios, so it should feel less repetitive. Each category has 10 scenarios now, and I added new ones like Work, Party, and Gaming. Chaos Mode actually works now too. Before it was mostly just a theme change, but now it randomly changes how much each choice affects your cooked score, so bad choices can get worse and sometimes weird stuff happens. I also added better endings based on your final score, so the results feel more personalized instead of just one basic ending. Current categories: School Sports Social Life Work Party Gaming Still planning to add more polish later, like stats, achievements, animations, and maybe better sharing.
Ships:
I made “Am I Cooked?”, a life simulator where your choices decide your future. The idea actually came from my friends we were brainstorming project ideas for me to make for stardance when one of them looked at something happening and said, “Bro, they’re so cooked.” We all laughed, and that’s how the idea clicked. The hardest part was getting all the choices and endings to work properly. I’m proud of turning a random joke into a fun, playable game with multiple paths. Try making different choices each time you play, and let me know if you find any bugs or have ideas to make it even better!...
|
1792821080.6320055
|
1792907480.6320055
|
|
56644
|
स्याउOS by @Kantarajluitel | Stardance
|
Kantarajluitel
|
1
|
22.79
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-03T02:23:16Z", "hours": 10.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Project Name: स्याउ OS (Syau OS) Creator: Kantaraj Luitel (Susant) Mission Guidelines Confirmation: Working Webpage with Draggable Windows: Full client-side desktop environment with multi-window support. Windows support 8 direction resizing, dragging, minimize, maximize, and z-index depth stacking. Original & Distinct Design: Custom visual identity combining bilingual typography (Noto Sans Devanagari + Space Grotesk + Inter) with a glassmorphism aesthetic. Features dual Dark and White Light themes, dynamic particle boot sequence with a Web Audio API chime, and canvas-based cursor trail. Devlogs (3+ Included): Embedded native “Devlogs” application inside the OS covering: Devlog 1: Architecture, Windowing Mathematics, and Non-blocking State. Devlog 2: Dual Light/Dark Theme Engine & Bilingual Typography Integration. Devlog 3: Canvas Performance, Responsive Layouts, and Mobile Adaptations. Unique Features Beyond the Guide: Pixel Cat Desktop Pet: Interactive canvas sprite with animation states (walk, idle, sleep, happy, blink) following the cursor. Custom Terminal Shell (syau-sh): Over 20 interactive commands including neofetch, matrix, cowsay, weather, and easter eggs. Embedded Spotify Music Player Hub with curated genres and custom link loader. Spotlight Search (Cmd+K / Ctrl+K), canvas-rendered analog clock widget, and Bikram Sambat date converter. Accessibility: No passwords or authentication walls; all applications and features are immediately accessible to test.", "repo": "https://github.com/susantedit/shayu-OS", "demo": "https://shyau.vercel.app/"}]...
|
[{"post_id": 76018, "ts": "202 [{"post_id": 76018, "ts": "2026-10-02T02:26:52Z", "hours": 1.8689, "text": "I broke down the stylesheet from one big file into clean, modular CSS files per component and app (src/styles/ and component-level CSS files like BaghChal.css, SyauType.css, FocusAudio.css). Removed redundant rules and cleaned up the class structure. Ready for re-review!"}, {"post_id": 72569, "ts": "2026-09-23T07:54:47Z", "hours": 3.9692, "text": "updates 3 feature for web os 2 1Handcrafted Vanilla CSS Window Manager 2Nepali Cultural Tools and Games 3coode editor"}, {"post_id": 67482, "ts": "2026-09-13T16:28:24Z", "hours": 6.3981, "text": "Wasted too much time on this i added nepali things convertor also go check it out cursor i added is just a image that i love and use on my pc always if you feel bad with it you can change it on the site :( sorry for late submission i was quiet busy and done this week now"}, {"post_id": 62576, "ts": "2026-09-06T01:19:07Z", "hours": 0.5533, "text": "UPdated the site in own taste"}, {"post_id": 60139, "ts": "2026-09-02T10:01:27Z", "hours": 8.3356, "text": "Shipped स्याउ OS (Syau OS) v1.3 for the WebOS Jam! 🚀 I wanted to make a web OS that feels alive, developer-friendly, and authentic to Nepal 🇳🇵. Here is what is new in v1.3: What I Built: • Syau Studio — Live in-browser Web IDE (HTML/CSS/JS sandbox with hot-reloading & retro templates) • Meo (स्याउ साथी) — AI OS Copilot (Groq Llama 3.3 / Gemini) + an interactive desktop pixel cat you can pet! • स्याउ Capture Studio — Screen recorder, canvas snip & markup tool, photo booth filters, and Web Audio waveform memo • Hardware Telemetry — Real battery status, power modes, and live Cloudflare DNS ping testing • Dual Theme Engine — Dark Glass & White Light mode + Nepali Bikram Sambat (BS) date converter • 100% Mobile Responsive — Works smoothly on phones, tablets, and desktops! Built with React 19, TypeScript, Vite, Tailwind CSS, Zustand & Framer Motion. Check it out on GitHub: https://github.com/susantedit/shayu-OS"}, {"post_id": 58805, "ts": "2026-08-31T12:01:56Z", "hours": 0.3556, "text": "🚀 Devlog #2: Making स्याउ OS Fully Responsive Across Web, Tablets & Mobile! 💡 The Big Update Simulating a full desktop operating system inside a browser comes with a major challenge: desktop windowing systems are typically built for large monitors and mouse pointers. But we know hackathon judges, contributors, and friends often open projects directly on smartphones, iPads, and split screens . Today, we officially rolled out v1.1.0-responsive , making स्याउ OS (Syau OS) adapt seamlessly across any device while keeping its signature frosted glass aesthetic and fluid Devanagari typography intact! 📱 What We Built & Optimized 1. 🪟 Adaptive Viewport Clamping & Auto-Maximized Windows On small screens (<768px), windows automatically adapt their width ( calc(100vw - 16px) ) and auto-maximize to fit the viewport. Bounding boxes are clamped so window titlebars and close controls never get pushed off-screen. 2. 🌊 Touch-Optimized Floating Dock Dock icons dynamically scale down and adjust spacing on smaller screens. Added smooth horizontal scroll with hidden scrollbars for mobile screens with high app density. Enlarged hitboxes so icons are easy to tap with a finger. 3. ⏱️ Responsive TopBar & Nepali BS Calendar Re-architected TopBar flex priorities: keeps the स्याउ OS brand logo, live Bikram Sambat (२०८३ BS) date widget, and Dark/Light mode switcher cleanly visible without overflowing on narrow screens. 4. 🍱 Fluid Bento Grids Across All Native Apps Creator Profile App (Kantaraj Luitel / Susant) : Bio, certifications, and Buy Me a Coffee button seamlessly collapse into single-column cards on phones. Drive Photo Gallery : 33 photos now arrange into an adaptive responsive masonry grid with touch-friendly lightbox previews. Devlog Viewer & Settings : Left sidebar and detail panes switch to a mobile-friendly view. 🛠️ Tech Stack & Implementation Highlights Framework : React 18 + TypeScript + Vite Styling : Tailored CSS Glassmorphism + Dynamic CSS Variables (Dark & Light White mode) State & Motion : Zustand + Framer Motion (touch drag bounds clamping) Typography : Noto Sans Devanagari 600 ( स्याउ ) + Space Grotesk 700 ( OS ) + Inter 👉 Check it out live and try resizing your browser or opening it on your phone! 🎉"}, {"post_id": 58716, "ts": "2026-08-31T08:04:32Z", "hours": 1.7383, "text": "स्याउ OS is a fast, web-based desktop OS built with React, TypeScript & Framer Motion for Hack Club Stardance. Features a window manager with 4 workspaces, Spotify Hub (Nepali, Bhajan, Phonk playlists), interactive terminal, store apps, devlogs viewer, and dual themes. Created by Kantaraj Luitel (Susant) 🇳🇵."}]...
|
Title: स्याउOS by @Kantarajluitel | Stardance
Dev Title: स्याउOS by @Kantarajluitel | Stardance
Devlogs:
स्याउ OS is a fast, web-based desktop OS built with React, TypeScript & Framer Motion for Hack Club Stardance. Features a window manager with 4 workspaces, Spotify Hub (Nepali, Bhajan, Phonk playlists), interactive terminal, store apps, devlogs viewer, and dual themes. Created by Kantaraj Luitel (Susant) 🇳🇵.
🚀 Devlog #2: Making स्याउ OS Fully Responsive Across Web, Tablets & Mobile! 💡 The Big Update Simulating a full desktop operating system inside a browser comes with a major challenge: desktop windowing systems are typically built for large monitors and mouse pointers. But we know hackathon judges, contributors, and friends often open projects directly on smartphones, iPads, and split screens . Today, we officially rolled out v1.1.0-responsive , making स्याउ OS (Syau OS) adapt seamlessly across any device while keeping its signature frosted glass aesthetic and fluid Devanagari typography intact! 📱 What We Built & Optimized 1. 🪟 Adaptive Viewport Clamping & Auto-Maximized Windows On small screens (<768px), windows automatically adapt their width ( calc(100vw - 16px) ) and auto-maximize to fit the viewport. Bounding boxes are clamped so window titlebars and close controls never get pushed off-screen. 2. 🌊 Touch-Optimized Floating Dock Dock icons dynamically scale down and adjust spacing on smaller screens. Added smooth horizontal scroll with hidden scrollbars for mobile screens with high app density. Enlarged hitboxes so icons are easy to tap with a finger. 3. ⏱️ Responsive TopBar & Nepali BS Calendar Re-architected TopBar flex priorities: keeps the स्याउ OS brand logo, live Bikram Sambat (२०८३ BS) date widget, and Dark/Light mode switcher cleanly visible without overflowing on narrow screens. 4. 🍱 Fluid Bento Grids Across All Native Apps Creator Profile App (Kantaraj Luitel / Susant) : Bio, certifications, and Buy Me a Coffee button seamlessly collapse into single-column cards on phones. Drive Photo Gallery : 33 photos now arrange into an adaptive responsive masonry grid with touch-friendly lightbox previews. Devlog Viewer & Settings : Left sidebar and detail panes switch to a mobile-friendly view. 🛠️ Tech Stack & Implementation Highlights Framework : React 18 + TypeScript + Vite Styling : Tailored CSS Glassmorphism + Dynamic CSS Variables (Dark & Light White mode) State & Motion : Zustand + Framer Motion (touch drag bounds clamping) Typography : Noto Sans Devanagari 600 ( स्याउ ) + Space Grotesk 700 ( OS ) + Inter 👉 Check it out live and try resizing your browser or opening it on your phone! 🎉
Shipped स्याउ OS (Syau OS) v1.3 for the WebOS Jam! 🚀 I wanted to make a web OS that feels alive, developer-friendly, and authentic to Nepal 🇳🇵. Here is what is new in v1.3: What I Built: • Syau Studio — Live in-browser Web IDE (HTML/CSS/JS sandbox with hot-reloading & retro templates) • Meo (स्याउ साथी) — AI OS Copilot (Groq Llama 3.3 / Gemini) + an interactive desktop pixel cat you can pet! • स्याउ Capture Studio — Screen recorder, canvas snip & markup tool, photo booth filters, and Web Audio waveform memo • Hardware Telemetry — Real battery status, power modes, and live Cloudflare DNS ping testing • Dual Theme Engine — Dark Glass & White Light mode + Nepali Bikram Sambat (BS) date converter • 100% Mobile Responsive — Works smoothly on phones, tablets, and desktops! Built with React 19, TypeScript, Vite, Tailwind CSS, Zustand & Framer Motion. Check it out on GitHub: https://github.com/susantedit/shayu-OS
UPdated the site in own taste
Wasted too much time on this i added nepali things convertor also go check it out cursor i added is just a image that i love and use on my pc always if you feel bad with it you can change it on the site :( sorry for late submission i was quiet busy and done this week now
updates 3 feature for web os 2 1Handcrafted Vanilla CSS Window Manager 2Nepali Cultural Tools and Games 3coode editor
I broke down the stylesheet from one big file into clean, modular CSS files per component and app (src/styles/ and component-level CSS files like BaghChal.css, SyauType.css, FocusAudio.css). Removed redundant rules and cleaned up the class structure. Ready for re-review!
Ships:
Project Name: स्याउ OS (Syau OS) Creator: Kantaraj Luitel (Susant) Mission Guidelines Confirmation: Working Webpage with Draggable Windows: Full client-side desktop environment with multi-window support. Windows support 8 direction resizing, dragging, minimize, maximize, and z-index depth stacking. Original & Distinct Design: Custom visual identity combining bilingual typography (Noto Sans Devanagari + Space Grotesk + Inter) with a glassmorphism aesthetic. Features dual Dark and White Light themes, dynamic particle boot sequence with a Web Audio API chime, and canvas-based cursor trail. Devlogs (3+ Included): Embedded native “Devlogs” application inside the OS covering: Devlog 1: Architecture, Windowing Mathematics, and Non-blocking State. Devlog 2: Dual Light/Dark Theme Engine & Bilingual Typography Integration. Devlog 3: Canvas Performance, Responsive Layouts, and Mobile Adaptations. Unique Features Beyond the Guide: Pixel Cat Desktop Pet: Interactive canvas sprite with animation states (walk, idle, sleep, happy, blink) following the cursor. Custom Terminal Shell (syau-sh): Over 20 interactive commands including neofetch, matrix, cowsay, weather, and easter eggs. Embedded Spotify Music Player Hub with curated genres and custom link loader. Spotlight Search (Cmd+K / Ctrl+K), canvas-rendered analog clock widget, and Bikram Sambat date converter. Accessibility: No passwords or authentication walls; all applications and features are immediately accessible to test....
|
1792846552.2506664
|
1793710552.2506664
|
|
33775
|
नभस्पंद by @orignalbatman | Stardance
|
orignalbatman
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: नभस्पंद by @orignalbatman | Stardance
|
1791823507.042878
|
1792687507.042878
|
|
54110
|
موقع "بنك الأسئلة للمذاكرة السريعة" (Quiz موقع "بنك الأسئلة للمذاكرة السريعة" (Quiz App) by @mntallhmhmd426 | Stardance...
|
mntallhmhmd426
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: موقع "بنك الأسئلة للمذاكرة السريعة" Title: موقع "بنك الأسئلة للمذاكرة السريعة" (Quiz App) by @mntallhmhmd426 | Stardance...
|
1792777712.6515005
|
1793382512.6515005
|
|
57209
|
مملكة الميزنية by @eyadkhalid383 | Stardance
|
eyadkhalid383
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: مملكة الميزنية by @eyadkhalid383 | Stardanc Title: مملكة الميزنية by @eyadkhalid383 | Stardance...
|
1792698477.7850292
|
1793303277.7850292
|
|
64132
|
тг бот by @egorgaramzin31 | Stardance
|
egorgaramzin31
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: тг бот by @egorgaramzin31 | Stardance
|
1792446547.8905518
|
1793051347.8905518
|
|
67884
|
ЯƎ⋊ƆAH by @sooraj | Stardance
|
sooraj
|
1
|
3.0
|
0
|
[{"ship_num": 1, "ts": "2026-1 [{"ship_num": 1, "ts": "2026-10-04T19:28:28Z", "hours": 3.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a cool looking hacker terminal based theme portfolio where visitors type commands instead of clicking links. Writing the JavaScript for the command inputs, auto-scrolling and setting up the text animation perfectly a liitle challenging . The text animation and the feeling like running a Linux terminal, complete with a dark theme and command not found errors. live link is given here and in github and if you don’t know what to type just type help in terminal.", "repo": "https://github.com/Sooraj44882/portfolio", "demo": "https://sooraj44882.github.io/portfolio/"}]...
|
[{"post_id": 76827, "ts": "202 [{"post_id": 76827, "ts": "2026-10-04T18:56:14Z", "hours": 1.3656, "text": "Devlog 3: added animation in terminal ,complete about,skill,project,contact section"}, {"post_id": 76729, "ts": "2026-10-04T13:04:05Z", "hours": 0.6414, "text": "Devlog 2: added the style to navbar and terminal screen and added the about section"}, {"post_id": 76712, "ts": "2026-10-04T12:11:03Z", "hours": 0.7022, "text": "Devlog 1:building portfolio added navbar and terminal use google fonts and style like hacker theme ,next i have to update the navbar and make a box like screen for terminal ,about,skill section"}]...
|
Title: ЯƎ⋊ƆAH by @sooraj | Stardance
Devlogs:
Dev Title: ЯƎ⋊ƆAH by @sooraj | Stardance
Devlogs:
Devlog 1:building portfolio added navbar and terminal use google fonts and style like hacker theme ,next i have to update the navbar and make a box like screen for terminal ,about,skill section
Devlog 2: added the style to navbar and terminal screen and added the about section
Devlog 3: added animation in terminal ,complete about,skill,project,contact section
Ships:
I made a cool looking hacker terminal based theme portfolio where visitors type commands instead of clicking links. Writing the JavaScript for the command inputs, auto-scrolling and setting up the text animation perfectly a liitle challenging . The text animation and the feeling like running a Linux terminal, complete with a dark theme and command not found errors. live link is given here and in github and if you don’t know what to type just type help in terminal....
|
1792817434.0627666
|
1792903834.0627666
|
|
66355
|
Протез by @Hmilkxx | Stardance
|
Hmilkxx
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Протез by @Hmilkxx | Stardance
|
1792460911.800177
|
1793065711.800177
|
|
27564
|
Опечатка by @FedShved | Stardance
|
FedShved
|
0
|
5.94
|
0
|
[]
|
[{"post_id": 18722, "ts": "202 [{"post_id": 18722, "ts": "2026-06-29T22:08:34Z", "hours": 0.7911, "text": "I set out to make the keyboard actually look like the design I’d settled on.Everything worked by then but it still wore a generic light theme, and the wholepitch is a keyboard that looks and types like Samsung’s, so the look had to land. Ipulled every color and a few sizing numbers into one theme object and repaintedthrough it: a black keyboard, near-black keys, white letters, and red used for onething only, the key you’re pressing. On top of that I added the pieces the mockupshowed — a floating preview of the letter above your finger, a permanent numberrow, a dim symbol in the corner of every key that you get by long-pressing, atwo-page ?123 layer, a blue enter key that turns into a magnifier in search boxes, arow of toolbar icons up top, and holding the spacebar to slide the cursor throughtext. The part I was wary of was the number row, because it doesn’t just sit on top, itgoes into the same grid the autocorrect uses to read where your taps land. Adding a fifth row shifts every letter’s position, and the worry was that it would quietlythrow off the typo-fixing and start mangling words. It turned out not to matter: thedecoder measures distances in key-widths rather than pixels, so adding oneevenly-sized row leaves the spacing between letters exactly what it was, and thedigits aren’t letters so they never enter the word search at all. The offline testthat runs thousands of fake typos came back with the same numbers as before thechange, false corrections still at zero, which is what let me put the row in the reallayout instead of bolting it on as a separate strip. The screenshot shows the new black keyboard with the number row on top and a pressedkey lit red with its letter popped up above it. Note, found while testing the redesign and not caused by it: two things in the decoder are worth fixing later. The bar offers “дом ас” when you type “домас”,because the run-together splitter will break a word in two as long as both halves are real, and “ас” happens to be a real word, so it peels it off even though that’s almost never what you want. And “домасний” won’t correct to “домашний”: that’s aс-for-ш mistake, but с and ш sit on opposite rows of the keyboard, and the auto correct only ever considers the key you hit and its close neighbors, so it never even weighsш as a possibility. The first is a small tuning fix; the second would mean teaching it to consider letter swaps beyond fat-finger range, which is a real feature and has to be done without breaking the zero-false-correction rule. ( the toolbar icons along the top aren’t wired up yet. The language one switches keyboards, but emoji, clipboard, settings, and the overflow menu are drawn for now and don’t do anything — they’re waiting for future wiring)"}, {"post_id": 18653, "ts": "2026-06-29T20:52:38Z", "hours": 4.0881, "text": "I wanted to close a gap that felt wrong in real use: autocorrect only ever looked at the word being typed right now. If a typo had already landed in the text and you tapped back into it, the keyboard just sat there and wouldn’t re-check the word or offer the right spelling. An earlier pass had made tapping into a word safe so it no longer mangled it, but the part you actually expect, tap the broken word and get the fix, wasn’t there yet. So now when the cursor lands inside a finished word the keyboard adopts it: it works out where the word starts and ends and, since the original taps are long gone, recreates them by dropping one tap dead-center on each letter’s key, then runs the same autocorrect search it uses while typing. The correct spelling shows up in the bar and one tap swaps it in where the word sits, without disturbing the spaces or words around it, and you can also just backspace and retype and it re-checks live. It never changes the word on its own - tapping in only offers a fix -which keeps the rule the whole project lives by, never correct a word that was already fine, intact at zero false corrections. The tricky part was telling apart the two times the cursor moves - when I move it, since right after committing a word the system reports the cursor now sitting after it, versus when you tap somewhere new. Treating my own cursor updates as a fresh tap made the keyboard re-grab and re-offer the word it had just finished, in a loop. I fixed it by remembering exactly where I last put the cursor and only reacting when it turns up somewhere I didn’t put it. The other half was being conservative about which words to touch: only plain Russian words, never names, numbers, or anything with characters that don’t exist on the keyboard, and never a half-typed fragment. Finally I was also able to fix a bug word-tearing. At first I had marked it done, but the exact thing that happens when you edit a word still broke. Type a word, press space, backspace into it, keep typing, and the keyboard treats the new letters as a separate new word and splits the old one in half. So I reproduced it on the emulator in the Settings search box, the field from the screenshots, and changed how typing into existing text works. Now when you start typing with the cursor inside a word the keyboard adopts that whole word and edits it as one unit instead of starting a loose fragment beside it, and I gave it a cursor index within the word so an inserted or deleted letter lands where the cursor actually is instead of always at the end. What slowed me down was that clean scripted taps would not tear the word no matter what I tried, which is the same trap I have fell into earlier. The bug was never in the path I kept testing. It only shows up once space has committed the word, and my reproductions weren’t pressing space first. Only after many many tries I was able to finally understand the logic of the bug. Space, then backspace, then type. With space, the word is committed text, so backspacing into it does plain deletes and the old code then composed only the new letter as its own fragment. Replacing that “cursor sits inside text” path with whole-word adoption fixed it, and false corrections stayed at zero the whole time since an adopted word is only ever offered, never swapped on its own."}, {"post_id": 17546, "ts": "2026-06-28T11:36:04Z", "hours": 1.0558, "text": "What I set out to do. Build the core of the keyboard: a full Russian ЙЦУКЕН layout that doesn’t just type letters, but fixes fat-finger typos as you go. The whole reason for this project is that Samsung’s Russian autocorrect is rough, so this part had to genuinely work, not just look the part. Drew the keyboard as a custom Canvas view instead of a UI framework, so it stays small and opens fast on old phones. Then wrote the autocorrect engine - it treats every tap as a point on the screen, not a fixed key, and runs a search over a word dictionary that scores how well your taps match each word against how common that word is. On space it decides whether to swap your typo for the best match. Never touch a word that’s already spelled right. At first the system said the keyboard was visible, the process was running, no crash in the logs, just a thin blank strip at the bottom. I lost a good while on this. Turned out Android measures the keyboard once with a width of zero before the real layout pass, and I was computing the keyboard’s height from its width, so zero width meant zero height and it never recovered. Fixed it by falling back to the actual screen width when the measured width comes back as zero. Keyboard popped straight up after that. (to be honest there are still problems with this system which i aim to soon fix, like for example starting mid word, or not spaced word. But at least I was able to get it to work in the most ideal conditions)"}]...
|
Title: Опечатка by @FedShved | Stardance
Devlogs: Title: Опечатка by @FedShved | Stardance
Devlogs:
What I set out to do. Build the core of the keyboard: a full Russian ЙЦУКЕН layout that doesn’t just type letters, but fixes fat-finger typos as you go. The whole reason for this project is that Samsung’s Russian autocorrect is rough, so this part had to genuinely work, not just look the part. Drew the keyboard as a custom Canvas view instead of a UI framework, so it stays small and opens fast on old phones. Then wrote the autocorrect engine - it treats every tap as a point on the screen, not a fixed key, and runs a search over a word dictionary that scores how well your taps match each word against how common that word is. On space it decides whether to swap your typo for the best match. Never touch a word that’s already spelled right. At first the system said the keyboard was visible, the process was running, no crash in the logs, just a thin blank strip at the bottom. I lost a good while on this. Turned out Android measures the keyboard once with a width of zero before the real layout pass, and I was computing the keyboard’s height from its width, so zero width meant zero height and it never recovered. Fixed it by falling back to the actual screen width when the measured width comes back as zero. Keyboard popped straight up after that. (to be honest there are still problems with this system which i aim to soon fix, like for example starting mid word, or not spaced word. But at least I was able to get it to work in the most ideal conditions)
I wanted to close a gap that felt wrong in real use: autocorrect only ever looked at the word being typed right now. If a typo had already landed in the text and you tapped back into it, the keyboard just sat there and wouldn’t re-check the word or offer the right spelling. An earlier pass had made tapping into a word safe so it no longer mangled it, but the part you actually expect, tap the broken word and get the fix, wasn’t there yet. So now when the cursor lands inside a finished word the keyboard adopts it: it works out where the word starts and ends and, since the original taps are long gone, recreates them by dropping one tap dead-center on each letter’s key, then runs the same autocorrect search it uses while typing. The correct spelling shows up in the bar and one tap swaps it in where the word sits, without disturbing the spaces or words around it, and you can also just backspace and retype and it re-checks live. It never changes the word on its own - tapping in only offers a fix -which keeps the rule the whole project lives by, never correct a word that was already fine, intact at zero false corrections. The tricky part was telling apart the two times the cursor moves - when I move it, since right after committing a word the system reports the cursor now sitting after it, versus when you tap somewhere new. Treating my own cursor updates as a fresh tap made the keyboard re-grab and re-offer the word it had just finished, in a loop. I fixed it by remembering exactly where I last put the cursor and only reacting when it turns up somewhere I didn’t put it. The other half was being conservative about which words to touch: only plain Russian words, never names, numbers, or anything with characters that don’t exist on the keyboard, and never a half-typed fragment. Finally I was also able to fix a bug word-tearing. At first I had marked it done, but the exact thing that happens when you edit a word still broke. Type a word, press space, backspace into it, keep typing, and the keyboard treats the new letters as a separate new word and splits the old one in half. So I reproduced it on the emulator in the Settings search box, the field from the screenshots, and changed how typing into existing text works. Now when you start typing with the cursor inside a word the keyboard adopts that whole word and edits it as one unit instead of starting a loose fragment beside it, and I gave it a cursor index within the word so an inserted or deleted letter lands where the cursor actually is instead of always at the end. What slowed me down was that clean scripted taps would not tear the word no matter what I tried, which is the same trap I have fell into earlier. The bug was never in the path I kept testing. It only shows up once space has committed the word, and my reproductions weren’t pressing space first. Only after many many tries I was able to finally understand the logic of the bug. Space, then backspace, then type. With space, the word is committed text, so backspacing into it does plain deletes and the old code then composed only the new letter as its own fragment. Replacing that “cursor sits inside text” path with whole-word adoption fixed it, and false corrections stayed at zero the whole time since an adopted word is only ever offered, never swapped on its own.
I set out to make the keyboard actually look like the design I’d settled on.Everything worked by then but it still wore a generic light theme, and the wholepitch is a keyboard that looks and types like Samsung’s, so the look had to land. Ipulled every color and a few sizing numbers into one theme object and repaintedthrough it: a black keyboard, near-black keys, white letters, and red used for onething only, the key you’re pressing. On top of that I added the pieces the mockupshowed — a floating preview of the letter above your finger, a permanent numberrow, a dim symbol in the corner of every key that you get by long-pressing, atwo-page ?123 layer, a blue enter key that turns into a magnifier in search boxes, arow of toolbar icons up top, and holding the spacebar to slide the cursor throughtext. The part I was wary of was the number row, because it doesn’t just sit on top, itgoes into the same grid the autocorrect uses to read where your taps land. Adding a fifth row shifts every letter’s position, and the worry was that it would quietlythrow off the typo-fixing and start mangling words. It turned out not to matter: thedecoder measures distances in key-widths rather than pixels, so adding oneevenly-sized row leaves the spacing between letters exactly what it was, and thedigits aren’t letters so they never enter the word search at all. The offline testthat runs thousands of fake typos came back with the same numbers as before thechange, false corrections still at zero, which is what let me put the row in the reallayout instead of bolting it on as a separate strip. The screenshot shows the new black keyboard with the number row on top and a pressedkey lit red with its letter popped up above it. Note, found while testing the redesign and not caused by it: two things in the decoder are worth fixing later. The bar offers “дом ас” when you type “домас”,because the run-together splitter will break a word in two as long as both halves are real, and “ас” happens to be a real word, so it peels it off even though that’s almost never what you want. And “домасний” won’t correct to “домашний”: that’s aс-for-ш mistake, but с and ш sit on opposite rows of the keyboard, and the auto correct only ever considers the key you hit and its close neighbors, so it never even weighsш as a possibility. The first is a small tuning fix; the second would mean teaching it to consider letter swaps beyond fat-finger range, which is a real feature and has to be done without breaking the zero-false-correction rule. ( the toolbar icons along the top aren’t wired up yet. The language one switches keyboards, but emoji, clipboard, settings, and the overflow menu are drawn for now and don’t do anything — they’re waiting for future wiring)...
|
1792680863.767333
|
1793285663.767333
|
|
32071
|
Дурак (Durak) AI Bot by @Madeincanada11 | Stardanc Дурак (Durak) AI Bot by @Madeincanada11 | Stardance...
|
Madeincanada11
|
0
|
0.28
|
0
|
[]
|
[{"post_id": 24116, "ts": "202 [{"post_id": 24116, "ts": "2026-07-07T14:08:00Z", "hours": 0.2792, "text": "Created main file, currently the program asks for a trump suit and then loops until the player enters the 6 cards that they have been dealt. If the user enters an invalid combo, the program rejects the answer and re-prompts them."}]...
|
Title: Дурак (Durak) AI Bot by @Madeincanada11 | S Title: Дурак (Durak) AI Bot by @Madeincanada11 | Stardance
Devlogs:
Created main file, currently the program asks for a trump suit and then loops until the player enters the 6 cards that they have been dealt. If the user enters an invalid combo, the program rejects the answer and re-prompts them....
|
1792777763.0874252
|
1793382563.0874252
|