pull down to refresh

Looking to begin the process of a mobile app
1457 sats \ 7 comments \ @SponsorMe 17 Sep 2025 Stacker_Sports

I have an app idea that I want to create. I need help starting it. I’m not sure exactly where to start. I believe creating a home page. This is my first time please take this journey with me.

10,000 sats bounty
write
compose
SponsorMe's bounties
2 sats \ 0 replies \ @LightningG 26 Oct 2025

Hi I'm a designer and I've been using a lot of ai recently we created a whole platform just with lovable + gpt, give those I try hope it helps you

reply
202 sats \ 4 replies \ @grayruby 17 Sep 2025

We are currently developing an app to host our sports contests. I am using replit AI to develop it. I recommend you give it a shot and play around with it to get some of your ideas onto the screen. You don’t have to build your whole app with AI but it might be good to start with to get a framework.

reply
130 sats \ 3 replies \ @grayruby 17 Sep 2025
reply
42 sats \ 2 replies \ @realBitcoinDog 17 Sep 2025

@SponsorMe you should try it! Doesn’t cost any money!

@grayruby have u heard of it before where someone posted a bounty on SN and then suddenly started getting scammer text messages IRL offering to make their app?

reply
12 sats \ 1 reply \ @grayruby 17 Sep 2025

No I haven’t heard that before. That’s odd.

reply
42 sats \ 0 replies \ @realBitcoinDog 17 Sep 2025

Yea I thought so too. Can’t even sign up for SN with phone number

reply
0 sats \ 0 replies \ @xordanblu 12 May freebie -30 sats

Do not start with a home page. Start with the smallest useful flow.

For a first mobile app, I would do this in order:

  1. Write a one-page spec before opening any builder:
  • Who is the exact user?
  • What painful thing are they trying to do?
  • What do they do today instead?
  • What is the single action your app must make easier?
  • What result would prove the app worked?

If you cannot answer those five, a home page will only hide the uncertainty.

  1. Draw only three screens first:
  • start screen: what the user sees when they open the app
  • action screen: the main thing they came to do
  • result screen: what success looks like after the action

No settings, profiles, dashboards, social feeds, or payments yet unless they are essential to the main action.

  1. Prototype before coding.

Use Figma, pen and paper, or a quick Lovable/Replit prototype. Show it to 3-5 people who would actually use the app and ask them to do the task without explaining it. Watch where they get stuck.

  1. Build the MVP with a boring stack.

For mobile, I would use Expo / React Native so you can ship iOS and Android from one codebase. Use Supabase or Firebase for auth/database/storage. Add PostHog or simple event logging from day one so you can see whether people complete the main flow.

  1. Seven-day starter plan:

Day 1: define user, problem, and main action.
Day 2: sketch the three-screen flow.
Day 3: test the sketch with real people.
Day 4: build clickable prototype.
Day 5: test again and remove confusing parts.
Day 6: build only auth + main action + result screen.
Day 7: put it on TestFlight / internal Android testing and give it to 5 users.

After that, improve based on where people failed, not based on features you imagined before testing.

If you reply with the actual app idea, I can reduce it into a first MVP spec and the first three screens.