|
60716
|
BLARE by @Skloofen | Stardance
|
Skloofen
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: BLARE by @Skloofen | Stardance
|
1792428576.8329628
|
1793033376.8329628
|
|
60714
|
My awesome macropad! by @bbk | Stardance
|
bbk
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @bbk | Stardance
|
1792428575.986075
|
1793033375.986075
|
|
60713
|
Wario-Ware! by @yummy_chicken784 | Stardance
|
yummy_chicken784
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Wario-Ware! by @yummy_chicken784 | Stardanc Title: Wario-Ware! by @yummy_chicken784 | Stardance...
|
1792428575.1395478
|
1793033375.1395478
|
|
60712
|
A obby by @jpmccaldon | Stardance
|
jpmccaldon
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: A obby by @jpmccaldon | Stardance
|
1792428574.2847626
|
1793033374.2847626
|
|
60711
|
WarioWare Game by @Maxw | Stardance
|
Maxw
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: WarioWare Game by @Maxw | Stardance
|
1792428573.4178092
|
1793033373.4178092
|
|
60710
|
WarioWare Game by @secrettayz | Stardance
|
secrettayz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: WarioWare Game by @secrettayz | Stardance
|
1792428572.5410185
|
1793033372.5410185
|
|
60709
|
My awesome macropad! by @Bhavyajain | Stardance
|
Bhavyajain
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Bhavyajain | Stard Title: My awesome macropad! by @Bhavyajain | Stardance...
|
1792428571.6237907
|
1793033371.6237907
|
|
60706
|
My awesome macropad! by @RARES09 | Stardance
|
RARES09
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @RARES09 | Stardanc Title: My awesome macropad! by @RARES09 | Stardance...
|
1792428570.7469857
|
1793033370.7469857
|
|
60705
|
Projects Kevin by @uzairfrancke10 | Stardance
|
uzairfrancke10
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Projects Kevin by @uzairfrancke10 | Stardan Title: Projects Kevin by @uzairfrancke10 | Stardance...
|
1792428569.7944136
|
1793033369.7944136
|
|
60704
|
Socle by @torren | Stardance
|
torren
|
0
|
77.41
|
0
|
[]
|
[{"post_id": 78912, "ts": "202 [{"post_id": 78912, "ts": "2026-10-12T00:46:52Z", "hours": 12.6531, "text": "Today was all about building and training the LLM behind Socle Intelligence, probably one of the most ambitious parts of Socle so far. The goal isn’t to make another AI chatbot that spits out generic advice. I’m building a system that can actually understand what’s happening inside a business by connecting customer experiences, employee performance, feedback patterns, and historical data. For example, if a customer says their food took forever but their server was amazing, the model needs to recognize two completely different signals: a potential operational issue and an employee who deserves recognition.I’ve been working on the model’s reasoning, training it to interpret feedback in context, experimenting with different parameters, and building the infrastructure that will eventually let business owners ask questions about their own data. The hardest part is getting the AI to distinguish between an isolated complaint and an actual emerging pattern, without making conclusions that the evidence doesn’t support. I’m also exploring local model deployment rather than relying entirely on external AI APIs, which adds another layer of complexity. The end goal is simple: turn thousands of individual interactions into intelligence that businesses can actually act on.Still plenty of work left, but this is where Socle starts moving beyond collecting data and toward understanding it."}, {"post_id": 76476, "ts": "2026-10-03T17:15:48Z", "hours": 10.4025, "text": "spent most of this session working on one of the bigger systems behind socle: the analytics/intelligence engine. the goal is basically to make sure socle does more than just collect feedback and throw a bunch of charts at a business. if someone scans a Snap, leaves feedback, recognizes an employee, saves a place, visits somewhere, or interacts with socle in another way, that creates a signal. the harder part is figuring out what those signals actually mean when you start connecting them together. so i started building out the system that takes those interactions and turns them into actual insights and suggestions. for example, instead of just saying “service mentions went down,” socle should be able to notice the pattern, look at what guests are actually saying, which types of guests are experiencing it, whether it is happening repeatedly or is just an outlier, and then suggest what the business could actually do about it. i also spent a lot of time on the explanation side of it. i really don’t want the dashboard to randomly spit out recommendations with no idea where they came from. every insight needs to have evidence behind it, so businesses can see why socle thinks something is happening, what signals contributed to it, and how confident the system is. if it gets something wrong, they should also be able to report that so we can keep improving the logic.the engine connects things like written feedback, selected responses, recognitions, interaction history, guest taste/context, repeated patterns, and changes over time. when multiple signals point toward the same thing, the system can treat that differently from one random interaction instead of pretending every piece of data means the same amount. i also worked on how this splits between the business and employee dashboards. managers need broader operational suggestions and patterns across the business, while an employee should get useful feedback about what they are doing well and what they could improve without just getting a weird analytics graph thrown at them.a big rule while building this has been no fake intelligence. if there is not enough evidence to make a useful conclusion yet, socle should say that instead of inventing one. right now a lot of the engine is deterministic/rules-based so i can actually test why every result appears. later i want to add an AI layer on top so businesses can ask questions directly and the system can reason across all of this context, but i want the underlying data and evidence system to be solid first.this is probably one of the first updates where the two sides of socle really start connecting together. the guest-facing product creates the interactions, Snap gives us another real-world interaction point, and the intelligence engine turns all of that into something a business can actually use.still a lot to build and test, but this is starting to feel a lot less like “analytics” and a lot more like the intelligence layer i originally wanted socle to become."}, {"post_id": 74662, "ts": "2026-09-27T21:53:50Z", "hours": 11.8033, "text": "spent around 11 hours on socle today, which is definitely over the devlog limit because i completely forgot to log before getting locked in 😭 this was one of those sessions where i fixed one tiny thing, noticed three more things that felt off, fixed those, then somehow found even more. i went through a bunch of screens and flows trying to look at everything like someone using socle for the first time instead of someone who already knows where every button is. i cleaned up spacing, navigation, loading states, interactions, weird edge cases, and a lot of smaller details that were not huge on their own but made parts of the app feel unfinished. there was not one massive new feature this time, but the app feels much more solid now. i think we are getting to the point where the remaining work is mostly about removing those little moments of friction that make a product feel rough, even if users cannot always explain exactly why. we were also hoping to ship this version, but we ran into some repo issues, so we are trying to figure out a cleaner solution before releasing it. hopefully we can sort that out soon and get this version out."}, {"post_id": 73283, "ts": "2026-09-24T19:07:21Z", "hours": 9.3703, "text": "spent around 9 hours going through socle and just fixing anything that still felt annoying, confusing, inconsistent, or unfinished. at this point a lot of the bigger stuff is already built, so i focused more on how everything actually feels to use. i went through different screens, flows, buttons, navigation, loading states, and smaller interactions and changed a bunch of things that were still kind of rough. a lot of the changes were pretty small by themselves, but together they made the app feel way smoother. i’m trying to get socle to the point where you don’t really have to think about the ui at all because everything just works how you expect it to. i also tried looking at everything more like a new user instead of the person who built it, which helped me catch a lot of stuff i was probably just used to seeing before. next i’m gonna keep cleaning up anything that still feels off, but i also want to start moving more time back into bigger features and systems again. then… SHIP IT!!"}, {"post_id": 72270, "ts": "2026-09-22T15:40:08Z", "hours": 8.9336, "text": "spent around 8 hours working mostly on the taste system and making it easier to actually test. the biggest thing i changed was visit system. since we don’t have the full location tracking system built yet, i replaced the old visit flow with a simple button for now. now we can actually test how visits affect someone’s taste without waiting for the full tracking system to be done. i also changed some of the math behind taste, mostly how different actions are weighted and how repeated activity is counted so one place can’t mess up someone’s entire profile. the screenshot below isn’t the exact equation or exact part i changed. i’m trying to be careful with how much of the scoring system i show. if you look at it and have no idea what’s going on, that’s kinda on purpose. i don’t want people to be able to reverse engineer it later or find ways to manipulate it if there are any loopholes we haven’t caught yet. next, i’m gonna keep testing the weights, keep doing ui/ux and qol polishes, and just keep fixing anything that still feels off before we bring in more testers."}, {"post_id": 71502, "ts": "2026-09-20T22:56:28Z", "hours": 9.3, "text": "spent around 9 hours doing another huge UI/UX polish pass on socle. at this point most of the main stuff is already there, so now i’m mainly finding all the smaller things that make the app feel unfinished. stuff like weird spacing, inconsistent layouts, interactions that feel a little off, small bugs, or certain parts of the app just not feeling as polished as everything else. for most of this session i was basically just going through the app over and over and fixing anything that felt wrong. cleaned up a bunch of layouts, fixed smaller UI/UX issues, changed some interactions, and reworked parts of the app that still felt kind of rough. i also added more locations and more content to existing locations so there’s actually more to explore when people start testing. that’s becoming more important now because as we bring in more testers, i don’t want them opening the app and running out of stuff to do after like 5 minutes. didn’t really add one massive new feature this time, but the app feels way better than it did before this session. everything is starting to feel a lot more complete now and we’re getting way closer to being ready for a much bigger testing wave."}, {"post_id": 70153, "ts": "2026-09-18T16:01:12Z", "hours": 6.0558, "text": "spent around 6 hours doing a big UI/UX cleanup across socle. i went through a bunch of different screens and just fixed a lot of the smaller things that felt off. stuff like weird spacing, layout issues, awkward interactions, inconsistent components, and parts of the app that still felt a little unfinished. i also cleaned up some of the navigation and made things easier to understand, especially for people using socle for the first time. most of the changes were pretty small on their own, but together they made the app feel way more polished and consistent. the main goal was just getting everything into a much cleaner and more stable state before we bring in a bigger wave of testers. i’d rather fix all the obvious stuff now so when people test it, their feedback is actually about the product and not random issues we already knew were there."}, {"post_id": 66671, "ts": "2026-09-12T15:11:08Z", "hours": 8.8928, "text": "this update was mainly focused on UI and UX. i used codex to help with some of the code implementation while i went through different parts of the app and tested everything. while testing, i found a few bugs in one of the features i had already built, so i went back and fixed those too. after the changes, the feature was working properly again and the overall experience felt a lot cleaner. next, i want to keep going through the app and completely get rid of any broken UI, bad UX, or annoying little issues. the goal is basically to get the QoL as close to perfect as possible before more people start testing it."}]...
|
Title: Socle by @torren | Stardance
Devlogs:
this Title: Socle by @torren | Stardance
Devlogs:
this update was mainly focused on UI and UX. i used codex to help with some of the code implementation while i went through different parts of the app and tested everything. while testing, i found a few bugs in one of the features i had already built, so i went back and fixed those too. after the changes, the feature was working properly again and the overall experience felt a lot cleaner. next, i want to keep going through the app and completely get rid of any broken UI, bad UX, or annoying little issues. the goal is basically to get the QoL as close to perfect as possible before more people start testing it.
spent around 6 hours doing a big UI/UX cleanup across socle. i went through a bunch of different screens and just fixed a lot of the smaller things that felt off. stuff like weird spacing, layout issues, awkward interactions, inconsistent components, and parts of the app that still felt a little unfinished. i also cleaned up some of the navigation and made things easier to understand, especially for people using socle for the first time. most of the changes were pretty small on their own, but together they made the app feel way more polished and consistent. the main goal was just getting everything into a much cleaner and more stable state before we bring in a bigger wave of testers. i’d rather fix all the obvious stuff now so when people test it, their feedback is actually about the product and not random issues we already knew were there.
spent around 9 hours doing another huge UI/UX polish pass on socle. at this point most of the main stuff is already there, so now i’m mainly finding all the smaller things that make the app feel unfinished. stuff like weird spacing, inconsistent layouts, interactions that feel a little off, small bugs, or certain parts of the app just not feeling as polished as everything else. for most of this session i was basically just going through the app over and over and fixing anything that felt wrong. cleaned up a bunch of layouts, fixed smaller UI/UX issues, changed some interactions, and reworked parts of the app that still felt kind of rough. i also added more locations and more content to existing locations so there’s actually more to explore when people start testing. that’s becoming more important now because as we bring in more testers, i don’t want them opening the app and running out of stuff to do after like 5 minutes. didn’t really add one massive new feature this time, but the app feels way better than it did before this session. everything is starting to feel a lot more complete now and we’re getting way closer to being ready for a much bigger testing wave.
spent around 8 hours working mostly on the taste system and making it easier to actually test. the biggest thing i changed was visit system. since we don’t have the full location tracking system built yet, i replaced the old visit flow with a simple button for now. now we can actually test how visits affect someone’s taste without waiting for the full tracking system to be done. i also changed some of the math behind taste, mostly how different actions are weighted and how repeated activity is counted so one place can’t mess up someone’s entire profile. the screenshot below isn’t the exact equation or exact part i changed. i’m trying to be careful with how much of the scoring system i show. if you look at it and have no idea what’s going on, that’s kinda on purpose. i don’t want people to be able to reverse engineer it later or find ways to manipulate it if there are any loopholes we haven’t caught yet. next, i’m gonna keep testing the weights, keep doing ui/ux and qol polishes, and just keep fixing anything that still feels off before we bring in more testers.
spent around 9 hours going through socle and just fixing anything that still felt annoying, confusing, inconsistent, or unfinished. at this point a lot of the bigger stuff is already built, so i focused more on how everything actually feels to use. i went through different screens, flows, buttons, navigation, loading states, and smaller interactions and changed a bunch of things that were still kind of rough. a lot of the changes were pretty small by themselves, but together they made the app feel way smoother. i’m trying to get socle to the point where you don’t really have to think about the ui at all because everything just works how you expect it to. i also tried looking at everything more like a new user instead of the person who built it, which helped me catch a lot of stuff i was probably just used to seeing before. next i’m gonna keep cleaning up anything that still feels off, but i also want to start moving more time back into bigger features and systems again. then… SHIP IT!!
spent around 11 hours on socle today, which is definitely over the devlog limit because i completely forgot to log before getting locked in 😭 this was one of those sessions where i fixed one tiny thing, noticed three more things that felt off, fixed those, then somehow found even more. i went through a bunch of screens and flows trying to look at everything like someone using socle for the first time instead of someone who already knows where every button is. i cleaned up spacing, navigation, loading states, interactions, weird edge cases, and a lot of smaller details that were not huge on their own but made parts of the app feel unfinished. there was not one massive new feature this time, but the app feels much more solid now. i think we are getting to the point where the remaining work is mostly about removing those little moments of friction that make a product feel rough, even if users cannot always explain exactly why. we were also hoping to ship this version, but we ran into some repo issues, so we are trying to figure out a cleaner solution before releasing it. hopefully we can sort that out soon and get this version out.
spent most of this session working on one of the bigger systems behind socle: the analytics/intelligence engine. the goal is basically to make sure socle does more than just collect feedback and throw a bunch of charts at a business. if someone scans a Snap, leaves feedback, recognizes an employee, saves a place, visits somewhere, or interacts with socle in another way, that creates a signal. the harder part is figuring out what those signals actually mean when you start connecting them together. so i started building out the system that takes those interactions and turns them into actual insights and suggestions. for example, instead of just saying “service mentions went down,” socle should be able to notice the pattern, look at what guests are actually saying, which types of guests are experiencing it, whether it is happening repeatedly or is just an outlier, and then suggest what the business could actually do about it. i also spent a lot of time on the explanation side of it. i really don’t want the dashboard to randomly spit out recommendations with no idea where they came from. every insight needs to have evidence behind it, so businesses can see why socle thinks something is happening, what signals contributed to it, and how confident the system is. if it gets something wrong, they should also be able to report that so we can keep improving the logic.the engine connects things like written feedback, selected responses, recognitions, interaction history, guest taste/context, repeated patterns, and changes over time. when multiple signals point toward the same thing, the system can treat that differently from one random interaction instead of pretending every piece of data means the same amount. i also worked on how this splits between the business and employee dashboards. managers need broader operational suggestions and patterns across the business, while an employee should get useful feedback about what they are doing well and what they could improve without just getting a weird analytics graph thrown at them.a big rule while building this has been no fake intelligence. if there is not enough evidence to make a useful conclusion yet, socle should say that instead of inventing one. right now a lot of the engine is deterministic/rules-based so i can actually test why every result appears. later i want to add an AI layer on top so businesses can ask questions directly and the system can reason across all of this context, but i want the underlying data and evidence system to be solid first.this is probably one of the first updates where the two sides of socle really start connecting together. the guest-facing product creates the interactions, Snap gives us another real-world interaction point, and the intelligence engine turns all of that into something a business can actually use.still a lot to build and test, but this is starting to feel a lot less like “analytics” and a lot more like the intelligence layer i originally wanted socle to become.
Today was all about building and training the LLM behind Socle Intelligence, probably one of the most ambitious parts of Socle so far. The goal isn’t to make another AI chatbot that spits out generic advice. I’m building a system that can actually understand what’s happening inside a business by connecting customer experiences, employee performance, feedback patterns, and historical data. For example, if a customer says their food took forever but their server was amazing, the model needs to recognize two completely different signals: a potential operational issue and an employee who deserves recognition.I’ve been working on the model’s reasoning, training it to interpret feedback in context, experimenting with different parameters, and building the infrastructure that will eventually let business owners ask questions about their own data. The hardest part is getting the AI to distinguish between an isolated complaint and an actual emerging pattern, without making conclusions that the evidence doesn’t support. I’m also exploring local model deployment rather than relying entirely on external AI APIs, which adds another layer of complexity. The end goal is simple: turn thousands of individual interactions into intelligence that businesses can actually act on.Still plenty of work left, but this is where Socle starts moving beyond collecting data and toward understanding it....
|
1792428568.4655888
|
1793033368.4655888
|
|
60699
|
kikiki by @jensel | Stardance
|
jensel
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: kikiki by @jensel | Stardance
|
1792428567.6192937
|
1793033367.6192937
|
|
60696
|
Klotski puzzle solver with 3D graph visuals by @Dy Klotski puzzle solver with 3D graph visuals by @Dynapart | Stardance...
|
Dynapart
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Klotski puzzle solver with 3D graph visuals Title: Klotski puzzle solver with 3D graph visuals by @Dynapart | Stardance...
|
1792428565.6314366
|
1793033365.6314366
|
|
60695
|
My own site! by @a_saif | Stardance
|
a_saif
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @a_saif | Stardance
|
1792428557.6503422
|
1793033357.6503422
|
|
60694
|
Orbit Dash by @SaiKernel | Stardance
|
SaiKernel
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Orbit Dash by @SaiKernel | Stardance
|
1792428556.7262383
|
1793033356.7262383
|
|
60693
|
carsim by @jensel | Stardance
|
jensel
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: carsim by @jensel | Stardance
|
1792428555.8522918
|
1793033355.8522918
|
|
60692
|
BUGATTI Brouillard by @nejenabinupa | Stardance
|
nejenabinupa
|
0
|
56.33
|
0
|
[]
|
[{"post_id": 71474, "ts": "202 [{"post_id": 71474, "ts": "2026-09-20T21:51:25Z", "hours": 5.0192, "text": "I added the rims and sum more materials and textures"}, {"post_id": 70088, "ts": "2026-09-18T13:08:04Z", "hours": 8.1472, "text": "I added sum more details adjusted sum things and added textures and materials to the modle and I need to make the wheels and more stuff"}, {"post_id": 69239, "ts": "2026-09-16T17:16:41Z", "hours": 7.0464, "text": "i added the grills and sum parts and i cut the sections sparest the panels"}, {"post_id": 68812, "ts": "2026-09-15T19:51:20Z", "hours": 9.5989, "text": "i make the sum parts in the car like headlights and enging bay"}, {"post_id": 67475, "ts": "2026-09-13T16:21:51Z", "hours": 8.6361, "text": "I make the back of the car and added sum more parts to to it"}, {"post_id": 65933, "ts": "2026-09-11T12:29:22Z", "hours": 9.3583, "text": "I make the back and and the said skirt and the wing"}, {"post_id": 65415, "ts": "2026-09-10T15:19:23Z", "hours": 8.5261, "text": "I’m starting from front, making the hood and the front bumper And looking good so far"}]...
|
Title: BUGATTI Brouillard by @nejenabinupa | Stard Title: BUGATTI Brouillard by @nejenabinupa | Stardance
Devlogs:
I’m starting from front, making the hood and the front bumper And looking good so far
I make the back and and the said skirt and the wing
I make the back of the car and added sum more parts to to it
i make the sum parts in the car like headlights and enging bay
i added the grills and sum parts and i cut the sections sparest the panels
I added sum more details adjusted sum things and added textures and materials to the modle and I need to make the wheels and more stuff
I added the rims and sum more materials and textures...
|
1792428554.870116
|
1793033354.870116
|
|
60691
|
Kb-slack-bot by @kbboy | Stardance
|
kbboy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Kb-slack-bot by @kbboy | Stardance
|
1792428553.9164946
|
1793033353.9164946
|
|
60689
|
My first slack bot! by @akshith_hya | Stardance
|
akshith_hya
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @akshith_hya | Stard Title: My first slack bot! by @akshith_hya | Stardance...
|
1792428553.0555243
|
1793033353.0555243
|
|
60686
|
CLOCKK by @anael | Stardance
|
anael
|
0
|
5.29
|
0
|
[]
|
[{"post_id": 67490, "ts": "202 [{"post_id": 67490, "ts": "2026-09-13T16:33:46Z", "hours": 3.0836, "text": "DEVLOG 2 I made the design which is kinda boring so in my next project i will try and improve my designs. I also wrote the firmware, but it was going over my head. That’s why I had to copy it from one of the other projects in this mission. Check my design out. (I named in slab clock cuz my design was like a solid box)"}, {"post_id": 65550, "ts": "2026-09-10T19:19:39Z", "hours": 2.2061, "text": "DEVLOG 1 Heyy! I just started the blare project and have done a decent amount of the work in just 2 hrs. I made the pcb which was kinda simple and also I started making the 3d model (I hate it). I kinda wish that there were a desk clock type of aesthetic screen in the component list, so that I could put it on my desk, but this works too. Check out the pcb design… (the yummers is a homelander ref btw)"}]...
|
Title: CLOCKK by @anael | Stardance
Devlogs:
DEVL Title: CLOCKK by @anael | Stardance
Devlogs:
DEVLOG 1 Heyy! I just started the blare project and have done a decent amount of the work in just 2 hrs. I made the pcb which was kinda simple and also I started making the 3d model (I hate it). I kinda wish that there were a desk clock type of aesthetic screen in the component list, so that I could put it on my desk, but this works too. Check out the pcb design… (the yummers is a homelander ref btw)
DEVLOG 2 I made the design which is kinda boring so in my next project i will try and improve my designs. I also wrote the firmware, but it was going over my head. That’s why I had to copy it from one of the other projects in this mission. Check my design out. (I named in slab clock cuz my design was like a solid box)...
|
1792428552.0779614
|
1793033352.0779614
|
|
60685
|
115OS by @doctamario85_tiktok | Stardance
|
doctamario85_tiktok
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 115OS by @doctamario85_tiktok | Stardance
|
1792428551.185629
|
1793033351.185629
|
|
60684
|
Stardex by @Mistix | Stardance
|
Mistix
|
0
|
1.0
|
0
|
[]
|
[{"post_id": 65462, "ts": "202 [{"post_id": 65462, "ts": "2026-09-10T16:34:24Z", "hours": 1.0028, "text": "DEVLOG-1 building my Alarm clocks pcb, wiring is the worst part :("}]...
|
Title: Stardex by @Mistix | Stardance
Devlogs:
DE Title: Stardex by @Mistix | Stardance
Devlogs:
DEVLOG-1 building my Alarm clocks pcb, wiring is the worst part :(...
|
1792428550.3111756
|
1793033350.3111756
|
|
60683
|
NYXAR by @kavya_yadav | Stardance
|
kavya_yadav
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: NYXAR by @kavya_yadav | Stardance
|
1792428548.6845756
|
1793033348.6845756
|
|
60681
|
AimScore by @vinodprabhashvara | Stardance
|
vinodprabhashvara
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: AimScore by @vinodprabhashvara | Stardance
|
1792428546.5753338
|
1793033346.5753338
|
|
60679
|
32x32 matrix by @priyanshusingh | Stardance
|
priyanshusingh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 32x32 matrix by @priyanshusingh | Stardance
|
1792428545.712544
|
1793033345.712544
|
|
60678
|
Frictionless by @ayaann068 | Stardance
|
ayaann068
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @ayaann068 | Stardance
|
1792428544.8236597
|
1793033344.8236597
|
|
60677
|
My first slack bot! by @oluwasefunmifarotimi | Sta My first slack bot! by @oluwasefunmifarotimi | Stardance...
|
oluwasefunmifarotimi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @oluwasefunmifarotim Title: My first slack bot! by @oluwasefunmifarotimi | Stardance...
|
1792428543.9092848
|
1793033343.9092848
|
|
60675
|
ATHENA by @auggie | Stardance
|
auggie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ATHENA by @auggie | Stardance
|
1792428543.0293145
|
1793033343.0293145
|
|
60674
|
Babyyyyyyyy by @manii | Stardance
|
manii
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Babyyyyyyyy by @manii | Stardance
|
1792428542.1269414
|
1793033342.1269414
|
|
60673
|
ASTRApad by @Kakkarotto | Stardance
|
Kakkarotto
|
0
|
1.94
|
0
|
[]
|
[{"post_id": 68005, "ts": "202 [{"post_id": 68005, "ts": "2026-09-14T11:17:27Z", "hours": 0.2503, "text": "redesigning guys"}, {"post_id": 66576, "ts": "2026-09-12T12:37:24Z", "hours": 1.6889, "text": "im started working on making a ASTRApad where i today designed the schematic build.now if there is any problem,pls feel free to comment and let me know"}]...
|
Title: ASTRApad by @Kakkarotto | Stardance
Devlog Title: ASTRApad by @Kakkarotto | Stardance
Devlogs:
im started working on making a ASTRApad where i today designed the schematic build.now if there is any problem,pls feel free to comment and let me know
redesigning guys...
|
1792428540.8615677
|
1793033340.8615677
|
|
60670
|
kind of minecraft alike by @rayane2 | Stardance
|
rayane2
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: kind of minecraft alike by @rayane2 | Stard Title: kind of minecraft alike by @rayane2 | Stardance...
|
1792428539.7591531
|
1793033339.7591531
|
|
60669
|
Dario by @ZonkCraft | Stardance
|
ZonkCraft
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Dario by @ZonkCraft | Stardance
|
1792428538.8964422
|
1793033338.8964422
|
|
60668
|
My very own WebOS by @amanwarrior96 | Stardance
|
amanwarrior96
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @amanwarrior96 | Stard Title: My very own WebOS by @amanwarrior96 | Stardance...
|
1792428537.8978624
|
1793033337.8978624
|
|
60667
|
Brain-Controlled Drone by @Marib | Stardance
|
Marib
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Brain-Controlled Drone by @Marib | Stardanc Title: Brain-Controlled Drone by @Marib | Stardance...
|
1792428536.956974
|
1793033336.956974
|
|
60666
|
EugeOS by @Euge | Stardance
|
Euge
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: EugeOS by @Euge | Stardance
|
1792428535.9649897
|
1793033335.9649897
|
|
60664
|
Gudov by @Qlz | Stardance
|
Qlz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Gudov by @Qlz | Stardance
|
1792428534.9985454
|
1793033334.9985454
|
|
60660
|
Website by @UnknowGamer | Stardance
|
UnknowGamer
|
0
|
2.83
|
0
|
[]
|
[{"post_id": 65379, "ts": "202 [{"post_id": 65379, "ts": "2026-09-10T14:12:41Z", "hours": 2.8333, "text": "Nothung"}]...
|
Title: Website by @UnknowGamer | Stardance
Devlog Title: Website by @UnknowGamer | Stardance
Devlogs:
Nothung...
|
1792428533.8808894
|
1793033333.8808894
|
|
60659
|
WarioWare Game by @ZzzWho | Stardance
|
ZzzWho
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: WarioWare Game by @ZzzWho | Stardance
|
1792428532.9368281
|
1793033332.9368281
|
|
60658
|
Frictionless by @Itjustme | Stardance
|
Itjustme
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @Itjustme | Stardance
|
1792428532.0001118
|
1793033332.0001118
|
|
60655
|
EpicOS by @Tyo | Stardance
|
Tyo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: EpicOS by @Tyo | Stardance
|
1792428531.0162168
|
1793033331.0162168
|
|
60654
|
My awesome macropad! by @kinglatrell0926 | Stardan My awesome macropad! by @kinglatrell0926 | Stardance...
|
kinglatrell0926
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @kinglatrell0926 | Title: My awesome macropad! by @kinglatrell0926 | Stardance...
|
1792428530.0412366
|
1793033330.0412366
|
|
60653
|
things I made ig by @anvay_purnaye | Stardance
|
anvay_purnaye
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: things I made ig by @anvay_purnaye | Starda Title: things I made ig by @anvay_purnaye | Stardance...
|
1792428528.9304016
|
1793033328.9304016
|
|
60652
|
things I made ig by @anvay_purnaye | Stardance
|
anvay_purnaye
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: things I made ig by @anvay_purnaye | Starda Title: things I made ig by @anvay_purnaye | Stardance...
|
1792428528.0628603
|
1793033328.0628603
|
|
60651
|
dreadai by @ckopweb | Stardance
|
ckopweb
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: dreadai by @ckopweb | Stardance
|
1792428522.9376972
|
1793033322.9376972
|
|
60648
|
Nightsight by @ingenious_daksh | Stardance
|
ingenious_daksh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Nightsight by @ingenious_daksh | Stardance
|
1792428522.0845625
|
1793033322.0845625
|
|
60647
|
Slack Bot by @laurenz | Stardance
|
laurenz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Slack Bot by @laurenz | Stardance
|
1792428521.2366683
|
1793033321.2366683
|
|
60646
|
Slack Bot by @laurenz | Stardance
|
laurenz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Slack Bot by @laurenz | Stardance
|
1792428520.378443
|
1793033320.378443
|
|
60643
|
My awesome macropad! by @gremlinns | Stardance
|
gremlinns
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @gremlinns | Starda Title: My awesome macropad! by @gremlinns | Stardance...
|
1792428519.4786212
|
1793033319.4786212
|
|
60642
|
My awesome macropad! by @laurenz | Stardance
|
laurenz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @laurenz | Stardanc Title: My awesome macropad! by @laurenz | Stardance...
|
1792428518.624979
|
1793033318.624979
|
|
60640
|
Preschool Showdown by @Arche | Stardance
|
Arche
|
0
|
2.69
|
0
|
[]
|
[{"post_id": 68139, "ts": "202 [{"post_id": 68139, "ts": "2026-09-14T16:05:23Z", "hours": 0.7669, "text": "Made the level screen, gonna work on making the screen actually function"}, {"post_id": 67331, "ts": "2026-09-13T12:17:22Z", "hours": 1.9236, "text": "Made the title screen and buttons. Also added the characters. They look goofy on purpose as honestly the game is made to be goofy on purpose. Thankfully i had already made one of the major characters for a prior project (it was an online hackathon but i was unable to use this as a mascot for it)."}]...
|
Title: Preschool Showdown by @Arche | Stardance
D Title: Preschool Showdown by @Arche | Stardance
Devlogs:
Made the title screen and buttons. Also added the characters. They look goofy on purpose as honestly the game is made to be goofy on purpose. Thankfully i had already made one of the major characters for a prior project (it was an online hackathon but i was unable to use this as a mascot for it).
Made the level screen, gonna work on making the screen actually function...
|
1792428517.7347221
|
1793033317.7347221
|
|
60637
|
off the map by @Lucashble | Stardance
|
Lucashble
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: off the map by @Lucashble | Stardance
|
1792428516.8806682
|
1793033316.8806682
|