@cassianomagnus: Agenda teu vídeo pro horário de pico 👆 posta até dormindo #crescernotiktok #dicastiktokbrasil #comoviralizar #constancia #tiktokdicas

Cassiano Magnus
Cassiano Magnus
Open In TikTok:
Region: BR
Saturday 26 September 2026 14:51:46 GMT
101695
2677
421
599

Music

Download

Comments

opaidaspromo
O Rei das Promo :
eu costumo criar os videos um dia antes e agendar manhã, tarde e noite
2026-09-26 15:27:43
12
eusouumponto
Geovane; :
tudo mentira
2026-09-26 17:20:28
8
republick.ttk
republick.ttk :
pessoas normais: "3 vídeos por dia horários de pico" eu: "vídeos agendados 1 vídeo por hora "
2026-09-27 08:58:36
7
geraldo.estevao38
Geraldo Estevao :
Quais são os melhores horários?
2026-09-26 22:08:08
9
monica.tamyres
Monica Veras 🇺🇸 :
Muito bom
2026-09-26 16:34:29
9
investidor.silva20
Investidor Silva | Dicas :
Qual horário vc prefere postar?
2026-09-26 16:35:06
7
brendaalencar1
Brenda | Achadinhos 🛍️ :
Mentira! pronto, ajudei no seu engajamento 😂
2026-09-27 12:37:46
6
anapaulaboroni7
Ana Paula Creator TikTokShop :
Muito boa a dica 🥰
2026-09-26 16:34:21
10
user532942596ana
MISSIONÁRIA:Anasilva Santos :
MARAVILHA
2026-09-27 02:09:37
6
josiventura7
JosyRodrigues :
não sabia, obrigado pela dica!
2026-09-26 18:45:23
5
mentalidade.pro2
kleber :
top demais eu nem sabia disso show parabéns
2026-09-26 18:16:16
7
dani_elevar_tikto
Dani_elevar_tiktok✨ :
gostei
2026-09-26 16:03:07
8
speedbuy.shop
Speedbuy Shop :
Muito boooom
2026-09-26 16:32:05
6
john_oficial04
☆𝐉𝐨𝐡𝐧☆ :
Socorro
2026-09-26 14:55:08
7
wendel.psi
Wendel | Psicólogo :
Boa dica
2026-09-26 16:00:09
5
estilohype.br
estilo.player :
ótima dica ! 👏
2026-09-26 15:18:24
6
mayla.vendas
Mayla Vendas :
temos que ter o tempo da edição, qiando necessário. Então, postar depois ajuda muito
2026-09-26 16:28:41
6
casacheia.cassiebru
Casa Cheia | Cassi&Bru :
Muito bom
2026-09-26 14:57:59
5
barbaracgsalles
Bárbara Salles :
Amigo, já postei em tudo quanto foi dia, horário, oração e não vai kkkkk
2026-09-27 03:26:59
5
eudaionorato2
Dai 🩷💖 :
Agendar os vídeos é oque me salva , como estou começando agora estou aprendendo tudo ainda, então gravo, agendo e consigo ter tempo de estudar pra aprender mais e melhorar meus próximos vídeos .
2026-09-26 16:39:12
10
deusa.digital
Deusa Digital :
Eu agendo tudo, até mesmo para testar os melhores horários
2026-09-26 20:43:54
9
podologaluanacaldin
Luana Caldin :
Eu sou mais simples 😂😂😂 posto qualquer horário... 30-50 vídeos de uma vez.
2026-09-27 10:54:43
8
daniellamatiasrod
Daniella Matias Rodr :
dica top
2026-09-27 14:28:31
6
eleneidesilva3
Ellen create :
Será
2026-09-27 13:29:29
6
alegattini55
ale Gattini 55 :
gostei da dica
2026-09-26 19:21:49
5
To see more videos from user @cassianomagnus, please go to the Tikwm homepage.

Other Videos

How to build an entire app with AI, the kind a developer charges $10,000 for You don't need to know how to code to build a real app. You need one idea first: every app has two halves. The restaurant: Front end = the dining room. Everything the customer sees and touches: the menu, the buttons, the booking form. In your app, that's the screens. Back end = the kitchen. The customer never walks in, but that's where the work happens: check the time slot is free, take the payment, save the booking, send the text. Database = the pantry. It stores every customer, every dog, every booking. Close the app, come back next week, and it's all still there. API = the waiter carrying orders between them. The screen asks, the back end answers. Most people only describe the dining room when they ask AI to build something. They get a beautiful app that forgets everything the second they hit refresh. The build, in Claude Code (a dog groomer's booking app): Plan: who it's for, the screens, what the kitchen does and what goes in the pantry, written to a plan file before any code. Front end: the booking page and owner dashboard, previewed in your browser. Point at what's off and it fixes it in seconds. Back end: a free Supabase project gives you two things, a web address for your database and a key. Keys go in one private file called .env: the key drawer in your back office. Then Claude Code connects the booking form and builds the tables. Log-in: email and Google, with Supabase handling the passwords. One rule, row level security: every customer only sees their own bookings. Test it by logging in as two different people. Getting paid: Stripe in test mode (play money). Copy the secret key into the drawer, ask for a $25 deposit with Stripe Checkout, test with 4242 4242 4242 4242. A webhook is Stripe calling your kitchen back to say
How to build an entire app with AI, the kind a developer charges $10,000 for You don't need to know how to code to build a real app. You need one idea first: every app has two halves. The restaurant: Front end = the dining room. Everything the customer sees and touches: the menu, the buttons, the booking form. In your app, that's the screens. Back end = the kitchen. The customer never walks in, but that's where the work happens: check the time slot is free, take the payment, save the booking, send the text. Database = the pantry. It stores every customer, every dog, every booking. Close the app, come back next week, and it's all still there. API = the waiter carrying orders between them. The screen asks, the back end answers. Most people only describe the dining room when they ask AI to build something. They get a beautiful app that forgets everything the second they hit refresh. The build, in Claude Code (a dog groomer's booking app): Plan: who it's for, the screens, what the kitchen does and what goes in the pantry, written to a plan file before any code. Front end: the booking page and owner dashboard, previewed in your browser. Point at what's off and it fixes it in seconds. Back end: a free Supabase project gives you two things, a web address for your database and a key. Keys go in one private file called .env: the key drawer in your back office. Then Claude Code connects the booking form and builds the tables. Log-in: email and Google, with Supabase handling the passwords. One rule, row level security: every customer only sees their own bookings. Test it by logging in as two different people. Getting paid: Stripe in test mode (play money). Copy the secret key into the drawer, ask for a $25 deposit with Stripe Checkout, test with 4242 4242 4242 4242. A webhook is Stripe calling your kitchen back to say "paid". The text reminder plugs in the same way with Twilio. Every outside service connects like this: account, key, drawer, sentence. Go live: push to GitHub, import into Vercel, paste the same keys into its settings, deploy. Buy your domain, add it in Vercel, copy two DNS lines into your domain company, and it's live on your own name with the padlock. Before real customers: point the webhook at the new address and swap test keys for live keys. After that, adding more is one sentence: Google Calendar sync, a loyalty card, review requests, or an automation that drops every new booking into your CRM. Your job becomes the owner who tests every button like a customer would. #buildwithai #claudecode #aiagent

About