Partner oficial de base44 (top 0,3%). Ayudo a negocios y coaches a lanzar apps, landings y pagos (Stripe/Mercado Pago) completos, sin código. Todo incluido.
¿Cuántas herramientas distintas pagas cada mes para sostener tu coaching?
Cursos en una, cobros en otra, reservas en una tercera. Cada salto entre ellas te cuesta alumnos. Mi plataforma, https://t.co/0GMEXVsvTw, lo lleva todo en un solo sitio.
https://t.co/B5fI16i8WT
@nagibaljeet Getting to TestFlight on day 3 is the hard part, most people stall before a build ever leaves their machine. The agent setup matters less than you think early on, what saves the most time is writing the spec for one screen at a time and locking it before moving to the next.
@travis_mcewan The people who complain about price are usually the ones least likely to buy twice, so they end up overweighted in the feedback and underweighted in the revenue. Raising it only for new traffic and leaving existing customers alone answers it in a week without burning goodwill.
@spinelessaisha Markdown files with frontmatter in a folder is the database, git gives you the history. 11ty isn't bloat, it runs at build time and ships nothing to the browser. You only need a real DB once you want to query across posts at request time.
@anymanfitness Predictability solves the hunger side. What still breaks people is the day training volume swings and the fixed number stops matching output. Keeping meal timing and structure identical while flexing only the carbs around sessions gets you both.
@raviojhax Not paranoia, that's a known trigger — any mention of a competing store or external payment gets flagged in review, even in unrelated copy like a gift card line. Appealing rarely works, genericizing the copy gets you through faster than fighting it.
@newworldkhaled Raw GPT vision guesses portions badly on its own. What actually moves accuracy is asking it to estimate volume against a reference object in the photo (plate, hand, fork), then matching that against a real food database instead of trusting the model's calorie number directly.
@SferlicRadu The one that gets missed even more often: PDP image load time on mobile. A page that takes 4+ seconds to show the product kills intent before any objection handling matters, the buyer is gone before they scroll to reviews.
Un plan de nutrición en PDF te da los mismos macros el día que entrenas pierna y el día que no te levantas de la silla.
Por eso en Macro+ los macros se recalculan cada día con la actividad real de tu wearable. El plan se adapta a ti, no al revés.
https://t.co/B5fI16i8WT
@DanWahlin Same failure mode with AI agents on other stacks: hand over the full spec and it makes silent assumptions between screens that surface three steps later. Locking one piece before the next catches those assumptions immediately.
Antes de aceptar un proyecto no te mando un presupuesto: te mando un boceto real y funcional en menos de 72h. Gratis, sin compromiso. Ves tu app funcionando en pantalla antes de que una agencia termine el PDF del presupuesto.
https://t.co/B5fI16i8WT
¿Cambiarías precios o descripciones de tu catálogo entero a la vez si no pudieras deshacerlo? La mayoría no se atreve, y por eso deja el catálogo a medio optimizar meses. ShopyHub guarda un snapshot antes de cada cambio masivo: rollback en un clic.
https://t.co/B5fI16i8WT
@wjacobs20301@peak_run_app With GPS trackers like this the real fight is battery, not UI: constant background tracking can drain a phone by early afternoon on the mountain. Worth checking if it throttles sampling when it detects you're stationary on a lift versus actually skiing.
@kcjr82 Same pattern I see constantly: when adding a feature costs nothing, everything feels justified. The skill that actually matters shifts from "can I build this" to "should this be in v1" — that's the part vibe coding doesn't do for you.
@kaido_xr La parte visual con IA está resuelta, pero producción en Shopify significa que el checkout, el inventario y las variantes aguantan sin fallos con tráfico real. Ahí es donde la mayoría de estos proyectos se quedan a medias aunque la web luzca impecable.
@dhtoran Me pasa igual con clientes que quieren su primera versión sin tocar código: vuela en lo fácil, pero en cuanto aparece un caso raro (un permiso, una integración rara) hace falta entender la estructura para pedirle el cambio correcto a la IA. Ahí se nota prototipo vs producción.
¿Has dejado algún plan de nutrición porque anotar cada comida pesaba más que prepararla? No es falta de disciplina, es fricción mal diseñada. Macro+ escanea el alimento entre 1M+ productos y calcula las macros solo, sin excusas para registrar.
https://t.co/B5fI16i8WT
@alsamahi Makes sense it holds up there — it's built by the same team that has to maintain it and knows exactly where the edges are. That's a different bar than shipping something a client's end users will hit cold with no context.