Loading...
Answers
MenuI want to develop a mobile application that is cross platform with good performance and design. Which technology should I use ?
I have experience developing desktop application and intranets for clients. I want to develop an app for IOS and Android with only one version of the code.
Answers
Hello I am an affiliate marketer and software developer and I recommend you call me because I know a never heard before free platform you can use to create your web app.
Either React Native or Flutter. I find developers for small businesses and startups, and those two are what I usually recommend to my clients. If you're going to do a web application in addition to mobile, I'd lean in favor of React Native over Flutter since you can do some common interface stuff with React. In terms of benchmarking, Flutter is usually faster than React Native, but in most cases either solution should work just fine.
I believe that Xamarin is the most complete cross-platform mobile app development framework, while .NET is an ideal development platform for the same.
Besides if you do have any questions give me a call: https://clarity.fm/joy-brotonath
I'd react-native anytime. It is easy to learn for devs, has a lot of resources online, and when it comes to delivery, it supports iOS and Android both. If you're in an early-stage company, react-native also helps you keep the costing low as possible, as compared to running 2 different teams and 2 different tech stacks for your mobile. We help our clients on building and scaling apps., reach out to me on how FirstPrinciples.io can help you develop your world-class app in a cost-effective way. If you're looking out for a cheaper solution, I'd suggest hiring a react-native developer from Upwork. Cheers.,
Assuming that this is not a "fun only" project and you have some broader professional and financial goals that you want to achieve with this app...
For the best answer, let's clarify and map out the circumstances of your question:
1. Who will be your client (who pays for your solution), and what kind of technological requirements they have?
2. Will you develop and also maintain/update the app? How frequently do you plan to roll out fixes, updates?
3. Who will be the users of your app? And how large will be your user base? What will be their preferences in using the app? Are there any specific
...
From all my venture building experience I learned, that even questions that seem purely technology-related, it' best to start with such high-level questions. Once you know all your preferences and requirements, it will be much easier to decide which technology stack will serve you best.
And if you did not yet decide on these high-level questions, then apply the startup studio framework. Because that will help you to discover a lot more hidden opportunities and potentials.
Related Questions
-
Where can I find programmers willing to join a growing mobile start up for equity only?
You won't find anyone worth adding to your team willing to work for equity only, no matter how compelling your product and business is. The realities of the talent market for mobile developers anywhere is such that a developer would be foolish to work only for equity unless they are a cofounder and have double digit equity. Happy to talk about hiring and alternatives to full-time hires.TW
-
Any opinions on raising money on Indiegogo for an app?
Apps are difficult to fund on IndieGoGo as few are successful, and we rarely take them on as clients. Websites like http://appsfunder.com/ are made for that very reason, but again, difficult to build enough of a following willing to pay top dollar for an app that could very well be free, already existing in the marketplace. A site that is gaining more traction you may want to look into would be http://appsplit.com/. Again, Appsplit Is Crowdfunding For Apps specifically.RM
-
If I am planning to launch a mobile app, do I need to register as a company before the launch?
I developed and published mobile apps as an individual for several years, and only formed a corporation later as things grew and it made sense. As far as Apple's App Store and Google Play are concerned, you can register as an individual developer without having a corporation. I'd be happy to help further over a call if you have any additional questions. Best of luck with your mobile app!AM
-
What tools to use for mobile Prototyping ?
My 2 favourite are: - www.uxpin.com - www.flinto.com Flinto is by far my favorite for mobile. I also us www.balsamiq.com for anything wireframe. Sometimes I jump into Sketch http://www.bohemiancoding.com/sketch/ for more high fidelity mockups using their Mirror feature http://www.bohemiancoding.com/sketch/mirror/ Hope that helps. P.S. There's a tonne of Mobile UX experts on Clarity, many $1/min - call them, you'll learn so much. my2cents.DM
-
Whats are some ways to beta test an iOS app?
Apple will allow a developer to register 100 UDID devices per 12 month cycle to test via TestFlight or HockeyApp. Having started with TestFlight, I would really encourage you NOT to use it, and go directly to HockeyApp. HockeyApp is a much better product. There is also enterprise distribution which allows you far more UDID's but whether you qualify for enterprise distribution is difficult to say. As part of your testing, I'd encourage to explicitly ask your testers to only register one device. One of the things we experienced was some testers registering 3 devices but only used one, essentially wasting those UDID's where we could have given to other testers. Who you invite to be a tester should be selective as well. I think you should have no more than 10 non-user users. These people should be people who have either built successful mobile apps or who are just such huge consumers of similar mobile apps to what you're building, that they can give you great product feedback even though they aren't your user. Specifically, they can help point out non obvious UI problems and better ways to implement particular features. The rest of your users should be highly qualified as actually wanting what you're building. If they can't articulate why they should be the first to use what you're building, they are likely the wrong tester. The more you can do to make them "beg" to be a tester, the higher the sign that the feedback you're getting from them can be considered "high-signal." In a limited beta test, you're really looking to understand the biggest UX pain-points. For example, are people not registering and providing you the additional permissions you are requiring? Are they not completing an action that could trigger virality? How far are they getting in their first user session? How much time are they spending per user session? Obviously, you'll be doing your fair share of bug squashing, but the core of it is around improving the core flows to minimize friction as much as possible. Lastly, keep in mind that even with highly motivated users, their attention spans and patience for early builds is limited, so make sure that each of your builds really make significant improvements. Happy to talk through any of this and more about mobile app testing.TW
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.