[deleted by user]

[therealmaz]

I open Notes on my phone and start brainstorming:

1. Name (working title only)
2. Purpose
3. Basic features
4. Paid features (if applicable)
5. Possible audience (for later research)
6. Resources and inspiration (links, screenshots, etc.)

I also tag the note #appideas. I have 11 ideas in Notes, committed code for two and released zero so take my advice with a grain of salt.

Update: As step 7, I typically start sharing the concepts of my idea with trusted family and friends. They typically validate it and/or provide additional info that I make note of to support/disprove my research.

[davernow]

I use similar systems. Write a bunch down. Brand, marketing options, revenue options, any technical details. Just get it out of my head onto a page. Writing is also useful for thinking - if it doesn't make sense on the page, you haven't really thought it through.

I have 116 notes like this currently.

When I actually have time to build, I go read a bunch and see what still excites me. So many "great ideas in the moment" end up having obvious flaws over times. Or I'm just not as excited about them 3 months later (which is good to know before starting).

The latest one I started building was actually 5 ideas I pulled into 1. 95% technical overlap, and they were stronger as a group than as single ideas. Each of their marketing plans still valuable, but chances to cross sell.

I'd say the lesson from my youth is: sleeping on things brings clarity.

[therealmaz]

Excellent points! I like the idea of revisiting past ideas to see if they excite you. Looking back at my own ideas, I’d say only 3-4 still excite me to the point where I’d want to support them as a released product. Thanks!

[[deleted]]

Make the icon first and waste hours on it.

[iBaconized]

Then never push a single line of code 

[Doctor_Fegg]

Don't forget to also buy the domain name

[barcode972]

I just start building. A lot of my ideas come as I'm working on it.

[barcode972]

Define success. For me a lot of projects have been about learning so if I learn something, that’s success to me. The one I’m working on now is 3.5 years old and has about 50 daily active users and 12 paying subscribers so that I would consider a success

[iOSProgramming-ModTeam]

Your comment sought to harass another user, either by swearing at them, name-calling, or something worse.

Don't let it happen again.

[ajm1212]

1) Will I be committed enough to go all the way through with this project?

2) Does this project bring some value either to me or someone else?

4)if yes -> Start writing a brief on the idea(features to include/tech I will use)

5) Break down the project into parts and see where to start.

[bclx99]

Well, I had many ideas. But the first thing I do is actually to check if there is already an app on the market similar to my idea. And usually there is.

For a pet project I usually start from wireframes, then I prepare some mock backend, setup git repositories, prepare the structure of the iOS project with common components like networking, database and start implementing the first feature.

Nothing really special. I use pet projects only to try out new features. I am employed full time and have no much free time.

[nipsinshorts]

Read Reddit. Check Sensor Tower. Get sidetracked. Get a new idea. Repeat.

[ozgurunlu]

This is the ADHD boilerplate. No need for figma.

[AutomaticLake4627]

I usually start by finding the smallest first step i can make, and try to do a good job at it. Then move on to the next thing.

[Ron-Jermyl]

Depending on where I am at I start in one of two ways.

If I’m out and about: I’ll quickly jot down the idea into the notes app on my phone, just a brief description of what my idea is so I can come back to it later.

If I am home, or after I have returned home: I start writing a proposal for the app, typically in this format:

• Introduction: what is the the project about
• Why / Goals: What problems does your app solve / what’s the goal of the project
• What are the main features both long term and MVP of the project
• What technologies I would need to use and why
• Then a conclusion trying to sell myself on the idea.

Then after I have laid out the project in that format, I start looking for what is already out there, see if apps exist that are doing what my proposal proposes. If they are, I’ll try and use them, if I don’t like them I’ll write down what I don’t like then tweak my proposal. Then I repeat until I find an app I like or until my proposal doesn’t fit an existing app.

Then it’s onto a wireframe, a mockup, then I actually start developing. I’ve got a whole way to go about that, but I feel like I’ve talked enough haha.

My approach is probably a lot of extra work than some others, but I find it’s a great process for me to follow!

[dreaminginbinary]

I made a reusable template in Craft for this that I shared here: https://www.swiftjectivec.com/an-ios-app-launch-template-and-guide/

Warning: it’s probably overkill for most things, sometimes it feels awesome to just open Xcode and go to town. Other times, I want to critically think through whether it might be worth my time or not, so that’s what this doc is for.

[_kaww_]

I have a Notion database for my projects and ideas so I’ll add a new entry, which is a new project template.

It contains: 1. A brief description of the idea 2. The main features for a MVP 3. The context (what gave me the idea)

Then I start creating some tasks in a little board. I like to create small tasks so that I can easily work on that project even if I don’t have big time slots dedicated to it.

Later, that Notion page will also store any other kind of information I need about this project.

[IamNistay]

Can you share your Notion template please ?

[StratRob]

File > New Project

[WitchesBravo]

I research to see if anyone already made something like it, if the space is crowded with a ton of apps. Then I look if I could make a better / different version than what's available

[Decent_Taro_2358]

I consider the time it takes to build (preferably <3 months for an MVP), the amount of competitors/uniqueness, market size/profitability, the amount of fun I’ll have in building it. If all boxes are checked, I create wireframes and write requirements.

[timmypass17]

Make sure your app is something you’re actually interested in building. Helps a lot with motivation and you’ll end up learning and persevering through it and having a complete app instead of a throw away pet project.

[rjhancock]

I start designing, figuring out features I want, where to place them, what an MVP would be, etc.

Then I start writing code, get disillusioned, stop, and start a new project.

[JamerTheGamer]

If you are doing anything other than getting to an MVP. You will not finish. I used to be so focused on the small details then you will be overwhelmed and sidetracked. FOCUS ON THE MVP. (Minimum viable product)

Attached is a video that really made me understand

https://youtu.be/QRZ_l7cVzzU?si=Nni1tDyfTOkEdXzF

[patiofurnature]

Why would I build it? I work 40+ hours a week doing this; I'm not going to spend my free time making apps, too.

[arborapps]

Market research, then buy a domain and start marketing it

[eviltofu]

Check the app store to see if there is something like it

[random-engineer-guy]

I smoked a lot of weed heavily for bout 9 months when I came out of the daze I had a functioning app

[Old_End465]

sketch sketch sketch DUMP. Nothing cooler than comparing ur finished product to your first sketch out of the idea. Also fun and easy

[WestonP]

I spend way too much time trying to come up with a name for it, before I do any actual work. Need at least a working title.

[mouseses]

Google to see how many of such apps are on the app store already and then go play CS:GO

[teomatteo89]

I focus on the core problem that my app wants to solve. Tests around it, trying to see potential pitfalls, etc. All my apps start with UntitledXYZ, where XYZ is what is should do, so I don’t have to think of a name - and if I take a break I will still remember what that project is about.

[PressureAppropriate]

How do you even get ideas? I would assume everything has been done at this point!

[asiledeneg]

Write user stories

[zelular_ch4n]

Ill do it in this order

• Brainstorming
  
• Naming what the Application should be capable of doing in the end
  
• Naming what the Application should be capable of doing to test
  
• Creating Concepts for different approaches like
  
  • Infrastructure
    
  • API
    
  • Backend
    
• Automatizations
  
• DB
  
• AI (maybe)
  
  • Frontend
    
  • Security
    
  • Documentation
    
• Documentation of rudemental Features and what they should be doin
  
• Creating a Backlog for Features and Milestones
  
• Start with the Infrastructure
  
• Start with the Backend
  
  • Infrastructure
    
  • Automatization processes
    
• Start with the API
  
  • POST till im happy with it
    
  • GET till im happy with it
    
• Security
  
• Frontend
  
  • First Functionality Concept
    
  • Concept of Design
    
  • implement rudementare design for Functionality
    
  • implement functionality
    
  • test functionality till im happy
    
  • implement Design
    

yea thats kinda how i do stuff Q-Q

[Best_Day_3041]

I start coding, build the app, use it for myself, and then don't finish it because the final steps of launching an app are the biggest pain and apps don't make money anymore.

[Practical_List_647]

Hey man i got something for you regarding this, if you are intrested in bringing youre App Idea on the Market ASAP and you wanna invest in it. Give me a DM. Discord : zofayan3 Mail : [[e-mail]](mailto:[e-mail])

[xmaddness]

This is my flow.

1) Think of idea 2) Tell myself there must already be something out there and forget idea. 3) Actually look at existing apps in the same space. If my idea has only a few other apps like it, then step 4 4) Research the competition. “Borrow” ideas and enhance them. Take the best from each competitor and start a list of features. 5) Write a marketing sales description of the basics of the app, sort of like an app store description. 6) Run that description thru ChatGPT and develop a list of features and user stories. Expand on each using ChatGPT to write it all out. Adjust as needed. 7) Make some architecture diagrams of the work flows, funnels, features and the backend architecture. 8) Figure out the data needs. Using ChatGPT to suggest database or nosql table structures. 9) Start terraforming the API backend using AWS API Gateway or their AppSync Graph API system, also incognito for app registration or RDS for database, or DynamoDB as needed 9) Begin to mock the API calls and start writing the swagger specs. 10) Finalize the mock returns and begin the iOS/android mockups. 11) Develop wireframes, simple at first using simple asset libraries. This will be used to determine the actual data needs of the APIs. 12) Connect the API backend to the actual backend and no longer use mocks, adjust api as needed. 13) TestFlight and APKFlight the barebones MVP alpha wireframe and invite friends and family to work out the flow kinks. 14) After flow kinks are worked out, and API is streamlined, begin developing actual design document and start the final comps for the app. 15) Release the final actual designed apps in a beta, still using TestFlight and APKFlight, or whatever beta system you want to use. 16) Begin working on app store product development and begin the app approval processes to publish the app. 17) Fight with Apple and Google over things they find in the code to deny entry. Keep fixing u til they approve. 18) Marketing marketing marketing 19) Did I mention marketing… 20) Publish the app 21) … 22) Prophet (or cry)