Ask me anything on Mobile Apps

@zameermfm Are you currently in search of a talented professional to join your team?"

@chikezie_sixtus Thank you for your consideration, but really sorry, as of now I'm not looking for a collaboration.

@zameermfm Thank you for letting me know. While you're not actively seeking a collaborator, I'm also open to remote job opportunities. If you come across any roles that require my skills and expertise, I'd appreciate it if you could keep me in mind. I'm eager to explore potential employment opportunities.

@chikezie_sixtus I don't have a venture as of now, this is a side project. I guess accountability and solid technical capability is a must-have for a remote worker.

@shajedulkarim_ Thank you, sure here are my insights, Common mistake in Mobile Apps in startups, Issues are mostly with MVPs, because they are the important piece of a mobile app based startup. 1. Over/Under development of features for MVP, i.e I have been part of a failed startup where we developed so many features for a long time, and it sort of went right into the grave. Lean startup model is always the way to go. And alternative failure is that features don't touch the bar due to resource constraints for MVP, and that too is a way to fail with mobile apps. 2. Design/development balance, If we cannot strike a balance between making sure designs can be developed quickly, it will eat up your development time unnecessarily. Always, the question needs to be asked and answered – will more development time into a particular screen/page design translate to business value? Seamless communication for offshore development, 1. A tip would be hiring the right/trustable person/agency, clear and concise requirements and two-way unfettered communication. 2. Product owner should always be you, tasks/project should always be managed by the product owner. So if you cannot have a technical/manager personnel on your side and want to fully outsource everything, it can be a recipe for disaster. Remote healthcare, As I see main disruption space is sensors interfacing with the system, I have worked with sensors devices which directly works with mobile, as well as sensors which are IoT (emitting to server). So mobile is a central device and there's an ecosystem around it. Balancing side projects, It's a battle, but I do when I get time, definitely I cannot do this year-round, there should be a cooling-off period. Atleast one small project per year :) Mobile tech, React native has never been out of trend, flutter is in the trend now. I don't think anything can go wrong picking either of the tech but depends on the requirements. Those sensors interfacing I've talked about earlier, I don't think you can find support for them in flutter since they are quite new. Expectation for numbertabs, Not much, I just want to see how numbers enough to break even the development cost :) Managing devs in startups, Yeah, you need to be clear about 80/20 rule and how to apply to situations, Design/development costs, Cost/benefit analysis on things. Communicating Product roadmap. Being transparent/collaborative/inclusive on process/features/decisions. Hope this helps!

@zameermfm so many interesting and useful insights mate, you’re super!

@scottlabsai it depends. Issues could arise from lack of testing, device sizes and densities etc. If you can be more specific, I can answer specifically. Is your app cross-platform?

@zameermfm Yes my app will be cross-platform. My fear is hidden costs of being on app stores that I might not be familiar with or any other hidden costs. My only cost for my app currently would be OAuth 2.0 verification to get a token for Venmo requests but I don't think that will be too expensive.

@scottlabsai Ok, You only have to worry about scaling when you have traction, but if you have a plan for monetization, then you are good. There will be other costs coming in future definitely, e.g, A good error monitoring tool/Analytics tool will cost you a bit, but that needs to come with scaling (in terms of users, as well as new features) and traction.