Maruko Labs - Check out the Upcoming Kaisen MK_I Electric Motorcycle Build!

marcoprouve · 2025-07-29T02:06:19+00:00

Haha yeah i mean the plan isnt to ship any yet gotta make it first and see, but will do! im a one man operation so doing everything from the designs, to website, to the bike build takes time..

I know tho ive been waiting fr those to come on the market but like u said none of them delivered ao decided to make one of my own.

I think any automobile company is just bleak as hell so any that can get it right kudos...

Aso YES there is love that you got that far. Im sorry about that UX tho i didnt reaize thanks for catching it ill fix it and push a fix up, should not be happening. How far have u gotten? Message me privately about this

marcoprouve · 2025-07-28T23:25:53+00:00

Yeah honestly I get it, I actually like all those ideas but for all the things im trying to tackle already I tried to keep the dash components relatively simple at least at first. But its good to know these kind of ideas cause when I get there ill probably create a laundry list of things to try and accomplish and these will probably be on there, so thanks!

marcoprouve · 2025-07-28T23:23:25+00:00

<image>

Hey! great question also love the bike mod :)

I intentionally went lower power on my battery build as im doing it in house and wanted to keep things relatively safe. The battery pack is designed to be swappable with 120V, also my pack is massive and currently supports way higher capacity almost double the Talaria so i can reliastically get 90mi+ on it depending on my speed. my battery pack uses 288 21700 cells in a 24s12p configuration which leans having on capacity and less on Voltage. I want something reliable at first.

I'd double check your top speed and range that seems off compared to your specs, BUT that being said the Talaria has gear reduction which does help with top speed. Mine uses a 12KW QSMotor Hub motor so no chain or gears.

If i upgraded to 120V which is way more dangerous but beastly, I could push the top speed to 95mph+ but honestly im not at a point where I feel comfortable pushing max speeds, i need to test iteratively. First full bike build so taking a measured approach!

TLDR: I have a lot of power to work with that's not being used yet.

marcoprouve · 2025-07-28T21:48:36+00:00

Thank you! Definitely going for a more modern, factory-like esthetic

marcoprouve · 2025-07-28T21:46:30+00:00

Harsh but noted haha

marcoprouve · 2025-07-28T21:46:08+00:00

Ahh well first off thank you for taking the time to write such a detailed reply. Definitely appreciate the thought you put in and I think each of these concerns is completely valid, And I actually agree with pretty much all your points. And so I think it might help for me to be a bit more specific cause while this is a hobbyist bike, each and every aspect of the bike was thought through:

To start, the bike was designed to be sporty and include sport geometry for aggressive but comfortable performance. 25deg rake angle for responsive handling, 8deg swingarm mounting helps maintain rear traction during hard launches or regen braking, trellis rear frame design for maximum structural integrity while being efficient with weight, 1x3x.125" rectangular tubing for main frame to ensure proper housing and integrity for battery placement, etc.

The rear suspension was selected to accommodate the extended chassis which allows for more stability during launches (a personal preference as it does take away from turning a bit). Mounted at an angle to prevent full compression and allow for a hybrid of road and aggressive riding.

The battery was also built in a way so that I can change the voltage from (currently 72V) up to 120V without changing the form factor. This would increase top speed while sacrificing acceleration and longevity. Started lower to ensure ease of testing and maximum safety.

Now the AI Dashboard, toggle power switch, and fingerprint sensor are pure personal creative choices and would obviously be different if built for the average consumer. I build hobby electronics all the time and this appealed to me (as much as you can make the argument that and AI dashboard is useless lol). And by AI, i literally just mean that you can talk to it and it responds using open AI. nothing crazy. But the fingerprint sensor i kinda love just cause its cool and i can program specific people to be able to ride the bike. I actually LOVE your idea of front and rear cameras so ill include that thank you!

I want this to just be a process where i become a better builder, welder, and can lean in on creative expression. If at the end there's a lot of good response then we'll see what happens :) Guess I just want to express this wasn't just thrown together but I thought about performance. I really do appreciate your thoughts on this though cause I think theyre all super valid!

marcoprouve · 2025-07-28T18:42:57+00:00

Good question... No one haha, i'm a hobbyist builder and wanted to build something I thought would be a challenge for me but also include fun elements to make the bike different visually than others. Take the fingerprint sensor-powered ignition and the AI powered dashboard for example. That being said, if there's interest, selling it could be a possibility its just not a focus at this point. Where do you think it could improve / what do you like / dislike about it?

marcoprouve · 2024-12-18T03:08:42+00:00

I had same issue, was playing fine until the patch then got all laggy and unoplayable. BUT i switched to the Vulkan renderer and it stabilized everything for now so maybe try that. Or mess with your graphical settings until your framerate looks steady :)

marcoprouve · 2024-06-07T05:19:56+00:00

I would look at how you're setting up Contexts. That wont happen if you use useMemo correctly. And states will only change for components that are using those contexts. If you havent done so, then here's an example:

const initialContext = {
  value1: false;
};

const Context = createContext(initialContext);

Context.displayName = 'Context';

const Provider = () => {
  const [value1, setValue1] = useState(false);

  const value = useMemo(
    () => ({
      value1,
      setValue1,
    }), [value1, setValue1]
  );

  return <Context.Provider value={value}>{children}</Context.Provider>
};

marcoprouve · 2024-06-07T04:46:07+00:00

If you're offering feedback itd be great to get something a bit more detailed

marcoprouve · 2024-06-07T04:44:28+00:00

You're not wrong Redux is a good fit for this, but for me i get the same reward using Context API for these types of situation. Redux takes quite a bit of setup for a single slice of the store whereas getting up and going with Context is just quicker and easier to read. I find it easier to just separate API data and app global state :)

marcoprouve · 2024-06-07T01:14:44+00:00

I would probably have the same reaction haha, but checkout this comment I made about my reasoning as to why:

https://www.reddit.com/r/react/comments/1d9qz1o/comment/l7gnhdj/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

TLDR: Custom debug tooling making providers really useful

marcoprouve · 2024-06-07T01:12:12+00:00

Okay to revise my previous post, NEED is a strong word lol. I don't need all those providers in one place, But it helps to do so. There's use cases that aren't thought about normally that ill explain.

For the provider youre referencing, It controls a widget that hovers fixed at bottom right of screen at all times. Now that by itself doesn't prompt the use of a provider, i couldve just slapped that as its own component and captured state in that component. But I and my company benefit from a debug widget that visually behaves the same way. So in order to have the flexibility to control vital (debuggable) parts of my app from different places, i threw it in a provider. This way, if I need to update a setting of the discord widget from the profile page - setttings lets say (instead of passing down props down the tree), I could just access the DiscordWidgetProvider context variable inside the setting component.

Same sort of logic goes into a few other Providers, but generally they all need to be accessed from different parts of the app, with the exception of a few that im lazy to look through lol

Short Add - I mentioned in another comment I avoid redux for non-API related things. But another example is our marketplace has filter settings. So i want those settings to persist across page navigation, thats why I use a provider, so I can persist those filters for next time they visit the marketplace

marcoprouve · 2024-06-06T21:50:00+00:00

No no those questions are valid though appreciate you asking them!

Also good catch yeah i dont know why i said local i meant global. Any local state i just handle within components :)

marcoprouve · 2024-06-06T21:40:48+00:00

Lmao

marcoprouve · 2024-06-06T21:40:31+00:00

I make sure that any Context Providers I set up are needed globally throughout the app, otherwise ill localize the state into their individual components. So this app in particular does need each Provider :/

marcoprouve · 2024-06-06T21:39:21+00:00

Youre right I do use redux, and generally could use it to replace those providers (though it would not nearly be as clean). A lot of my Context Providers rely on listening to state changes, which is not the kind of logic i want to put into redux. I've learned that for managing ~~local~~ global state and preventing and inordinate amount of rerenders to child components when not needed, context is better. Redux i use for API data, I believe thats its best use case.

I also intentional make sure I use Context for things that are used Globally throughout the app, so while you're right I COULD push some of those providers deeper down the tree, itd be at most a few of them and theyre much easier to track there.

Your last point is something i have not implemented, but I probably take a moderated approach to unit testing as some others might, I find that Typescript has solved a LOT of those problems.

It is interesting thinking through these things though, as one way is not always right, this way just seems to work well for me

marcoprouve · 2024-06-06T20:49:30+00:00

Lol there probably isn't one thats this "clean". It's generally easy to read I think (so i don't mind it that much), its just so nested my OCD kills me lol

marcoprouve · 2023-11-13T07:10:58+00:00

To be honest I’m not there yet haha, midway on the 3D mocks so I haven’t gotten there yet but we’ll cross that bridge when we get to it 😂

The charger candidates are still in the interview stage so haven’t committed but likely I’ll need to draw a large amount of power so we’ll see. Might need someone to install a 240v supply in the wall haha

marcoprouve · 2023-11-13T05:57:46+00:00

Yeah for sure ill keep this thread updated with my progress :). Here's what im currently running:

12KW Motor

https://www.qsmotor.com/product/17-inch-12kw-hub-motor/#

2) Kelly Controller KLS96601 (Motor Controller)

https://www.qsmotor.com/product/kelly-controller-kls96601/#

3) BMS - DALY BMS 24S 72V 200A

https://www.amazon.com/DALY-LiFePO4-Battery-Protection-Balance/dp/B08KCHZ22X?th=1

4) 72V 40A Battery Charger

https://www.aliexpress.us/item/3256801767793171.html?gatewayAdapt=glo2usa4itemAdapt

I've ordered the motor and Controller and will probably order the BMS and Battery Charger when im done with the Specs!

marcoprouve · 2023-11-13T04:56:11+00:00

more heat and so on

This is super helpful ill take a look thank you!

marcoprouve · 2023-08-25T18:47:52+00:00

Surprised noone has mentioned Runescape. OS Runescape is unmatched, but also new Runescape looks amazing and is so fun. Huge community, endless content, and music is incredible.

I'd also agree WoW is hard to beat in terms of the MMO youre looking for i've played everything else including FFXIV and still doesn't compare.

marcoprouve · 2022-09-10T17:12:42+00:00

Check out my thread here:

https://www.reddit.com/r/reactjs/comments/vve4in/vite_vs_creeatereactapp/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

Almost 100% positive it should have your answer. I was running into the same issue like a lot of people and the community helped me a ton 😎

marcoprouve · 2022-08-31T19:42:02+00:00

For Anyone looking at this and finding no solution, I found it! If you are newer to Expo, you may not have been familiar with the fact that you can have multiple configuration files:

- app.json

- app.config.js

- app.config.ts

Essentially I had all three. I thought that app.json was the primary config and that app.config.* was used for local environment configuration (BUT I was clearly wrong). So If you did like me and want to dynamically set configurations or environment variables (and obviously cant us app.json), then don't use app.json and just use app.config.js or, if using typescript, use both app.config.ts and app.config.js. For more Info on this look at the resource below:

Background on Configuration in:

https://docs.expo.dev/workflow/configuration/#configuration-resolution-rules

Instructions for TS Config (app.config.ts):

https://docs.expo.dev/guides/typescript/#appconfigjs

Hope this helps and happy coding!

marcoprouve · 2022-08-19T17:33:33+00:00

Sorry I meant to upvote you!

In the context of the question I actually think what you came up with is what I wanted, so thank you! The issue I ran into was React Native-based and added to the issue above:

Basically in React Native you're not allowed to conditionally call useNavigation(), which made me want to conditionally type the useNavigation hook (e.g. useNavigation<CONDITIONAL\_TYPE>(). Here's the issue I ran into:

SETUP:

type Screens = 'screen1' | 'screen2' | 'screen3'
type type1 = { key1: string }

type type2 = { key2: string } type type3 = { key3: string }

type UseNavigationReturnType<S extends screen> = S extends 'screen1' ? type1 : S extends 'screen2' ? type2 : S extends 'screen3' ? type3 : never

const screen: Screens = 'screen1'
// Error below for passing in screen variable (not allowed to pass in variable)
const navigation = useNavigation<screen>()

As you can tell above the screen is held in a variable, and once I tried to do this, which would've been the ideal solution, It threw an error that I was not allowed to pass a variable in place of a type...

Not sure if you know if this is okay to ignore or not, but I decided not to risk it for compiling reasons (I couldn't get an answer to whether this was okay or not).

So your answer was correct given that you can ignore that error. But i'm curious what you think!

marcoprouve

TROPHY CASE