You know what you need to do.
But you still can’t start.
That gap is what I’m building StuckShift for.
Not a planner.
Not a habit tracker.
Not a big productivity system.
Just a small app that turns a stuck thought into one first move you can start within 24 hours.
Looking for early testers.
Reply with one thing you’re stuck on, or DM me “first move”.
#StuckShift
You know what you need to do.
But you still can’t start.
That gap is what I’m building StuckShift for.
Not a planner.
Not a habit tracker.
Not a big productivity system.
Just a small app that turns a stuck thought into one first move you can start within 24 hours.
Looking for early testers.
Reply with one thing you’re stuck on, or DM me “first move”.
#StuckShift
me just like this weird kid right now :((
little bit tried, code over 11 hr (perhaps i need to rest ....)
btw the book name is Head First Software Architecture, it help me build the Architecture mindset
checking the security of my app , perhaps the landing page and the app coming soon ⁉️⁉️
Curious other builder how many hour coding per day 🧐😜
#BuildinPublic #LearningJourney
Looking to connect with people who are actually building and shipping.
🗣️Founders.
🗣️Indie app creators.
🗣️Developers.
🗣️Growth people.
🗣️Mobile app builders.
I’m building StuckShift and learning in public.
Say hi 👋
#buildinpublic#indiedev
I spent too long thinking about how to promote StuckShift.
This week I finally did the obvious thing:
I posted.
Not viral.
Not polished.
Not a master strategy.
Just daily small experiments.
The interesting part is not the follower count.
The interesting part is the signal:
some people resonate with “I know what to do but still can’t start.”
That is the audience I’m trying to understand.
Marketing, for now, is not about scaling.
It is about finding the language real people already use when they feel stuck.
#BuildInPublic #IndieHackers #StuckShift
Your app can leak secrets without a single UI bug.
One Flutter security mistake I’m learning:
don’t print sensitive data into debug logs.
Bad pattern:
Future<void> login(String email, String password) async {
final response = await authService.login(email, password);
print('Email: $email');
print('Password: $password');
print('Access token: ${response.accessToken}');
print('Full response: $response');
}
The app may run perfectly.
Login works.
The screen changes.
The user gets in.
But the logs may now contain data that should never be exposed.
I’m learning to be careful with:
— passwords
— access tokens
— refresh tokens
— API keys
— full API responses
— private user input
The question I now ask is simple:
“Am I logging the event, or am I logging the secret?”
Logging:
“Login success”
is different from logging:
“Access token: abc123…”
Not an expert.
Just learning not to leak sensitive data while debugging.
PM me “SECURITY” if you want the prompt I use to review this.
#Security #Flutter #mobileapp
@calicojonez5ajj I respect this mindset.
When the reason is bigger than yourself, procrastination starts to look different.
It is not just “I’ll do it later.”
It becomes “what future am I delaying?”
Yup i got you
Sometimes procrastination is not about the task being too hard.
It’s about what the task forces you to face:
who you were, who you’re trying to become, and the fact that you’re still somewhere in the middle.
That middle place can feel uncomfortable enough to make avoidance feel easier.