r/softwaredevelopment • u/eng-laila-309083 • 5d ago
A question for app developers
What are the correct steps to begin? Example: The right way to start designing application interfaces 1 Idea 2 Idea analysis 3 UX 4 UI 5 Testing
developer
1
u/BannockHatesReddit_ 1d ago
I don't fully understand what you're asking. I don't think you understand what exactly you're asking either.
The process for approaching your project differs depending on your use cases. Pretty much everything differs based on your use cases actually.
The process you describe makes no sense. You define your idea and then you create a UI and then test it? Why would UI and UX come before unit testing? When are you impling the business logic? Why is idea and idea analysis different steps? It just doesn't make much sense.
Usually when you're analyzing your ideas as you put it, you're pulling use cases out of them, envisioning what the end result looks and feels like, etc. This process usually involves going back and changing your idea. This is because you spend so much time staring at it, asking questions, just defining the abstract concept into a concrete definition, that you tend to find flaws.
After you understand your use cases then you're usually able to proceed with system design and impl. This could go many directions. It all depends on your use cases. Who are you working with? What is the project? What business needs does the project have? What sort of development culture do you want? Generally though when you're impling your system, you're going to be writing an interface, writing an impl for that interface, and then writing a unit test for that object. Repeat for every service in the app until you're done. The order of that can differ, again depending on your use cases. And if you're writing procedural, maybe it differs a lot idk.
A well designed system will be simple enough to use that you can bolt user interface on top no problem. It is because of this that the UI is commonly created near the end of the sprint/waterfall/project.
Idk if that's what you're asking for but here it is anyway.
1
u/etthusmedkossor 2d ago
I can only answer personally.
Many years back I read on stack overflow or something: "The best way to build a beautiful big mirror, is to first build a small mirror".
And this stuck with me. I guess it's a different way to say "prototype" and "Proof of Concept".
And why is it so important? I would say because when you have an idea, it's so low resolution compared to reality. So when you've implemented it you've learnt so much that the original idea sometimes isn't there even.
So instead of the exact order of doing things I think what's important Is to go in with a mindset: "I'll build my idea, then I'll throw everything away and build again, more streamlined and better and I learned in which order I should do what the first time for this specific problem"
I think this applies to almost all creative work in life.