Loading...
Answers
MenuI am a new fish in the User experience design for mobile application business. Should I learn web design and html?
Is it necessary for me to learn web design and some html to land a good job in other parts of the world in any leading agency? App design is the only thing I like to do.
Answers
If app design is the only thing you'd like to do, then I'd say spend all your time and focus developing UI/UX expertise for mobile. In many developing nations around the world, smart devices are giving people their first exposure to the Internet. The way they search, browse, buy, and otherwise behave online hasn't been profoundly shaped by desktop computing (and all the extra real estate that larger screens afford). All that to say, I've begun to think of UI/UX design for mobile as a distinct discipline. Many fine web designers find it very difficult to make the transition over to mobile: almost like fiction writers trying to write poetry. Starting with web and moving to mobile may actually handicap you. But if you start by learning to be economical and use limited mobile real estate to its best effect, then you'll probably be a better web designer (if you decide to grow into it later) for it.
Hope this helps,
Austin
To me U/X consists of many things – design/look-and-feel, navigation, content, information architecture, etc. Certainly it would help if you have design skills and HTML experience but you need to understand from a user’s perspective how they interact with the app and their needs. U/X is the overall experience that an user has while interacting with an app. It is not just one thing that will make the user experience great but rather the total of many different components.
For instance, if the navigation is really well thought out but the content is not that relevant when they get to a page, then the U/X is poor.
Worry about the product and how you will make it.
Don't stop taking massive action.
Best of Luck,
Michael T. Irvin
michaelirvin.net
My books are available exclusively through Amazon Books. Check out my book "Copywriting Blackbook of Secrets"
Copywriting, Startups, Internet Entrepreneur, Online Marketing, Making Money
You should learn Web designing. Web designing is an Art. It has become more popular than before. Now-a day’s everyone is creating their own websites for professional and personal use. Here are some reasons and benefits of how studying web designing course can benefit your career. Website designing is extremely easy to be trained. If you are interested to start your profession as a web designer, you must first undergo proper training before you can master it. There are many quality trainings centres available in your locality. It is extremely easy for people those who have prior designing knowledge and artistic talent. Web designing is not just creating web page to display content and image.
HTML learning can be beneficial as well. Learning HTML can be used for situations like formatting a blog or email, working with a CMS, embedding external content on your site, and creating usable content. In the same vein, knowing HTML is like making sure you are fully prepared for a vacation. Knowing HTML can save you hours of frustration, precious time with your design team, or even money dealing with an external contractor. Use HTML to create internal links. This is an easy hack to do yourself if you know HTML. If you know HTML, you will know how to embed content in the first place, not to mention troubleshoot any issues if the content is not appearing correctly.
Besides if you do have any questions give me a call: https://clarity.fm/joy-brotonath
Related Questions
-
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!Alec MorganaAM
-
Is it ok from a brand perspective to have different color schemes for your logo for different purposes?
Building a brand takes more than a logo. With that said, consistency is key for obtaining a competitive advantage that speaks to your market for longer. I would recommend against using different styles and colors for various purposes and instead maybe avoid using in lieu of the logo use maybe instead borders or patterns that use your logo's or brand colors. The idea of a logo is to engrave a mission or product into potential customers when they simply see the brand or logo... Once a logo is pushed and promoted you can strengthen that image by enforcing the brands colors through different materials or media :)Humberto Valle Texas Real Estate Investor, Wholesaler, & Airbnb SuperhostHV
-
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.Dan MartellDM
-
What is the best technology for developing a new mobile app from scratch?
There are two sides to that question. One is the mobile app itself and the other is the backend. If I misunderstood in any way and you didn't mean "native" app I apologize in advance. On the backend, there is no clear cut answer to which is the "best". It depends solely on the developers you are able to get. We for example use Node.js , mongoDB, redis, elasticsearch and a couple of proprietary tools in the backend. But you have your pick of the litter now both on the backend api and the datastore with the myriad of options available and touted as the "best" currently on the market. Now on the app side again it solely depends on what you need your mobile app to do. Experiencing first-hand "develop once, run anywhere" I can say it's more like "develop once, debug everywhere" to quote a Java saying. We have tried Phonegap and Titanium Appcelerator and we have switched to native (ObjC and Java) after a couple of months of trying to go the hybrid route. The reasons behind the choice are as follows: - anything that breaks the pattern of how those frameworks NEED to operate is just a huge technical debt that keeps accruing a huge interest. - anything that uses css3 accelerated animations on Android is buggy at best and slow as hell at worst on any lower (< 4.1 I think) versions of Android I hope this gives you some insight. If you need/want to ask me anything feel free to contact me. MihaiMihai PocorschiMP
-
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.Tom WilliamsTW
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.
_SQUARE.jpg?1626983158)