¿Puedo vibecodear Bevel?

PARCIAL · un fin de semana
precio $14.99/mesahorrarías $179.88/añotiempo de build un fin de semanacategoría 🧘 bienestarreemplazada por 0 personas

Bevel is not sitting on secret data: it reads the same HealthKit records your watch already wrote, then does math and draws charts. An agent can absolutely build you a local dashboard over an Apple Health export that computes rolling averages, sleep and HRV trends, and lag correlations between habits and recovery. The gap is delivery, not analysis: real HealthKit access means an actual iOS app, Xcode, a developer account and background sync, and manual export zips get stale fast. You also lose the part Bevel spends most of its effort on, which is turning noisy sensor data into something you glance at once a day and actually understand. Fine for a curious quantified-self person, annoying for anyone who wants a phone widget.

el prompt
Build a local Apple Health analytics dashboard. Single machine, no accounts, no cloud, no telemetry.

Stack, non negotiable: Python 3.12, DuckDB for storage, Streamlit for the UI, uv for dependency management. No web framework, no Docker, no database server.

Project layout:
- ingest.py: CLI that takes a path to an Apple Health export.zip
- app.py: Streamlit dashboard
- health.duckdb: local database file, gitignored
- .env for anything configurable (default export path), read with python-dotenv

Ingest requirements:
- Read export.xml directly from inside the zip, streaming, using xml.etree.ElementTree.iterparse and clearing elements as you go. The file can be 500MB+, never load it into memory.
- Extract Record elements and Workout elements. Normalise into two DuckDB tables: records(type, source, unit, start_ts, end_ts, value) and workouts(activity_type, start_ts, end_ts, duration_min, energy_kcal).
- Strip the HK prefixes off type names so they read as sleep_analysis, heart_rate_variability_sdnn, resting_heart_rate, step_count, active_energy_burned, respiratory_rate, oxygen_saturation, body_mass.
- Idempotent: re-running on the same export replaces the tables, does not duplicate.
- Print a summary of row counts per type and the date range found.

Dashboard requirements:
- Date range picker, defaults to last 180 days.
- Daily aggregate table built in SQL: steps sum, active energy sum, resting HR mean, HRV mean, sleep hours from sleep_analysis asleep intervals, workout minutes.
- One chart per metric with a 7 day rolling mean drawn over the raw daily points.
- A correlation panel: pick metric A and metric B, pick a lag of 0 to 3 days, show the Pearson r, the n, and a scatter plot. Print a blunt caption saying this is correlation on a tiny sample and means nothing on its own.
- A weekday breakdown: mean of each metric by day of week.
- No composite "scores", no AI summaries, no advice text. Numbers only.

Deliver a README with the exact export steps from the iPhone Health app, the uv commands to run ingest and the dashboard, and one paragraph stating clearly that this needs a manual re-export to stay current and is not medical advice.

$ ábrelo en tu agente (prompt listo, tú das enter) o cópialo crudo

Se puede en parte

Ahorro de referencia: US$180/año si dejas de pagar Bevel.

Quiero que lo armen →
por qué la gente sigue pagando

Because the value of health metrics collapses if you have to go fetch them. Bevel's job is to be already updated when you open your phone, with a number you trust and a sentence that explains it. A local notebook that needs a manual export every two weeks answers different questions: interesting once, abandoned by month two. People pay for the part that keeps running when their curiosity does not.

qué pierdes

xLive background sync; you are re-exporting a zip by hand

xA phone app, widgets and notifications

xTheir opinionated composite scores and plain-English daily readouts

xNon-Apple device integrations and whatever normalisation they do across sources

xCharts that a designer looked at

arte previo · úsalo en vez de construir, si prefieres

Nada que valga la pena señalar. Por eso existe el prompt.

compartir en X ↗"Acabo de reemplazar Bevel ($14.99/mes) con un prompt"
preguntas
¿Puedo vibecodear Bevel?

Parcial. El núcleo de Bevel se arma en un fin de semana con el prompt de esta página, pero hay huecos reales: Live background sync; you are re-exporting a zip by hand, A phone app, widgets and notifications. Lee la lista honesta arriba antes de comprometerte.

¿Cuánto cuesta Bevel?

Bevel cuesta unos $14.99/mes (Bevel Pro, revisado 2026-08-18), o sea $179.88 al año.

¿Qué pierdo si reemplazo Bevel?

Con honestidad: Live background sync; you are re-exporting a zip by hand; A phone app, widgets and notifications; Their opinionated composite scores and plain-English daily readouts; Non-Apple device integrations and whatever normalisation they do across sources; Charts that a designer looked at. Si alguno de esos te sostiene el negocio, sigue pagando.

¿Hay una alternativa open source a Bevel?

No hay una alternativa open source madura que valga señalar. Por eso existe el prompt de esta página.

Cada semana mueren más suscripciones.

Veredictos nuevos, prompts nuevos, las apps más condenadas de la semana.
Un correo. Te sales en un clic.

gratis para siempre · sin spam · el prompt se queda en el sitio, las muertes te llegan a ti

$semanal: qué recibió veredicto, qué murió.