Contact person: React Native Wheel & Calendars

Phone:Show

Email:Show

Location: Vienna, Austria

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I have two connected tasks that I’d like completed in React Native.

Task 1 – Wheel control
I need a flat, non-3D “wheel” or picker component that accepts an items prop that can arrive either as a simple string array or as an array of objects containing value and label; I’ll rely on the component to handle both transparently. Whether the list loops back to the first item when the user scrolls past the end should be configurable because sometimes I’ll want a seamless loop and other times a hard stop.

Essential props
• items: string[] | {value,label}[]
• loop: boolean
• strings: number – always coerced to an odd count (e.g. 4 → 5) so the selected row sits in the middle
• selected: string | value
• disabled: string[] | value[] – I might reference items either by label or by value, so both options must work

Event
• onChange fires with the currently selected label or value, matching the form of the original items array.

Task 2 – Two calendar pickers built on that wheel
Using the same wheel component internally, I need:
1. A regular calendar that inputs/outputs dates in “dd-mm-yyyy” format.
2. A Hebrew calendar with the identical “dd-mm-yyyy” external interface but internally using the Hebrew date system. To know how many days of month of year use "hebcal" library

Both calendar pickers must expose the selected date via the same onChange signature as the wheel and accept a default value prop. Visual consistency with the wheel control is important.

What I expect to receive
• Reusable, well-typed React Native components (TypeScript preferred)
• Clean, commented source with no external native modules beyond standard React Native + community date libs (e.g. moment-hijri, date-fns, or similar)
• A quick demo screen showing the wheel in isolation and each calendar in action
• Basic README explaining props, expected formats, and an example import

I’ll integrate the components into an existing app, so clarity and maintainability are key. Let me know any framework or library assumptions before you begin coding." (client-provided description)